-
Notifications
You must be signed in to change notification settings - Fork 14
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
Support pods? #4
Comments
Hm, there is also the opposite problem of import paths pointing into the component js files, that may be hard. |
But I think most things that import components are probably components, so if we just migrate all components and update their outbound import paths correctly, that should be 99% good enough. |
FWIW, the import paths already need to be rewritten. |
For those who land on this issue, I wrote a codemod to un-pod Ember projects. Feel free to give it a try. |
@ijlee2 holy shit, that was quick. You told me about this in planning just a few hours ago. 👏 |
@buschtoens Been working on it since Wednesday. 😄 |
It would be good to support migrating from pods into the new structure, so that we can encourage people to migrate. In order to move js files, we would need be able to parse the imports and update any relative imports correctly.
The text was updated successfully, but these errors were encountered: