-
Notifications
You must be signed in to change notification settings - Fork 12k
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
application
builder unable to resolve import
#27841
Comments
This is expected behavior. |
Ahhh ok, I had worried that was the case. Thanks for the clarification! |
Previously, ESM file resolution without extensions failed when using Vite, causing issues in module loading. This commit addresses the problem by automatically resolving `.mjs` files, aligning the behavior with the application builder and ensuring consistent module resolution across different build tools. Closes angular#27841
Previously, ESM file resolution without extensions failed when using Vite, causing issues in module loading. This commit addresses the problem by automatically resolving `.mjs` files, aligning the behavior with the application builder and ensuring consistent module resolution across different build tools. **NB**: This is a workaround as valid ESM imports should always have an extension. Closes angular#27841
Note: We will add a workaround for Again, this is a workaround since valid ESM imports must include a file extension. |
Previously, ESM file resolution without extensions failed when using Vite, causing issues in module loading. This commit addresses the problem by automatically resolving `.mjs` files, aligning the behavior with the application builder and ensuring consistent module resolution across different build tools. **NB**: This is a workaround as valid ESM imports should always have an extension. Closes #27841 (cherry picked from commit 2324d5a)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Command
serve
Is this a regression?
The previous version in which this bug was not present was
No response
Description
When using the new
application
builder, runningng serve
fails at runtime if any code from the package[email protected]
is used. This same package/version works using the legacy builder.Minimal Reproduction
Create a new angular project
Install the following package
Use an export from this library
Exception or Error
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: