That would allow for platform implementations to diverge though and experiment before standardizing common functionality. This is starting to feel like a web standards proposal now 🤔
October 30, 2025 at 4:06 AM
That would allow for platform implementations to diverge though and experiment before standardizing common functionality. This is starting to feel like a web standards proposal now 🤔
…Namespaces could help here if we failed builds when unimplemented directives are found. Some directives might get standardized and moved to the global namespaces.
This reminds me of vendor prefixes in CSS though, so I’m a bit hesitant.
October 30, 2025 at 3:59 AM
…Namespaces could help here if we failed builds when unimplemented directives are found. Some directives might get standardized and moved to the global namespaces.
This reminds me of vendor prefixes in CSS though, so I’m a bit hesitant.
In a monorepo, multiple frontends could be deployed on different platforms. In this case the lines get blurry and it’s unclear what code is and isn’t portable between projects. The code deploys fine, but doesn’t behave the same…
October 30, 2025 at 3:54 AM
In a monorepo, multiple frontends could be deployed on different platforms. In this case the lines get blurry and it’s unclear what code is and isn’t portable between projects. The code deploys fine, but doesn’t behave the same…
Yeah, namespaces could help with that. Like “vercel: use workflow”. Tanner mentioned this too, but that doesn’t fully solve the problem because it’s still up to everyone to cooperate. Better than just all global though.
October 30, 2025 at 2:44 AM
Yeah, namespaces could help with that. Like “vercel: use workflow”. Tanner mentioned this too, but that doesn’t fully solve the problem because it’s still up to everyone to cooperate. Better than just all global though.
I think we do need to solve for some of the issues Tanner raised though. Like having an ergonomic syntax for options and being able to differentiate between language and platform-/framework-specific annotations. If we can solve that with directives, great, but I haven’t seen any good proposals yet
October 30, 2025 at 1:04 AM
I think we do need to solve for some of the issues Tanner raised though. Like having an ergonomic syntax for options and being able to differentiate between language and platform-/framework-specific annotations. If we can solve that with directives, great, but I haven’t seen any good proposals yet
That’s a fair point. Counter argument though: we already have restrictions around placement of hooks even though they’re just regular functions and we use lint rules to enforce placement. We could do the same here.
October 30, 2025 at 1:02 AM
That’s a fair point. Counter argument though: we already have restrictions around placement of hooks even though they’re just regular functions and we use lint rules to enforce placement. We could do the same here.
What concerns me most about directives is it’s not clear which ones are a language feature vs a platform/framework feature, and if you move your code between platforms that both have “use workflow” but diverging implementations, then things can break unexpectedly even though the code is identical.
October 30, 2025 at 12:28 AM
What concerns me most about directives is it’s not clear which ones are a language feature vs a platform/framework feature, and if you move your code between platforms that both have “use workflow” but diverging implementations, then things can break unexpectedly even though the code is identical.