-
-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V2 App #977
base: master
Are you sure you want to change the base?
V2 App #977
Conversation
@NullVoxPopuli one important thing this has to mention - Ember Engines. |
It's possible "structure" would be a layer on top of this. Like, "structure" is a convention would an overlaying tool could enforce / provide ergonomics on top of. I plan to make a prototype of what I mean next week 🤞 |
I would propose that v2 apps behave like astro islands by default, meaning that you can have multiple apps on a page at once without each of them bringing their own runtime along this would turbo charge the concept we have today as 'engines' as well as fit well into the desire to have a clear way to boot such an app both webpack and vite have plugins that support module federation which is one way to achieve this goal |
I'm a huge fan |
also here is a mind blowing fact credit to @kategengler for knowing that addon exists |
Yeah and in a few years the trend will be to switch back from single-file class/template to separate class and template files. |
I sure hope not. |
Co-authored-by: MrChocolatine <[email protected]>
Co-authored-by: MrChocolatine <[email protected]>
we should consider how we have tests running in v2 format one problem space I see is with Worker (web workers; service workers etc) that can use one consideration would be to have the test runner and app in completely separated server instances and do the work to wire up the tools to get a similar level of productivity you get today from tests - but how that looks exactly I'm not sure |
wip, ready for comments, suggestions, tho, as the details still need worked out