-
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
Build error after upgrading from 18.0.6 to 18.2.3 #28390
Comments
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Sep 11, 2024
…dencies by Vite This commit excludes Node.js module imports from being processed by Vite when prebundling is enabled. Closes angular#28390
alan-agius4
added a commit
to alan-agius4/angular-cli
that referenced
this issue
Sep 11, 2024
…dencies by Vite This commit excludes Node.js module imports from being processed by Vite when prebundling is enabled. Closes angular#28390
alan-agius4
added a commit
that referenced
this issue
Sep 11, 2024
…dencies by Vite This commit excludes Node.js module imports from being processed by Vite when prebundling is enabled. Closes #28390
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
Getting the following error after upgrading from 18.0.6 to 18.2.3. Not sure whether it's issue from Angular or Azure Storage Blob.
To Reproduce
Steps to reproduce the behavior:
@azure/storage-blob
packageimport { BlockBlobClient } from '@azure/storage-blob';
in one of the componentExpected behavior
No error to occur.
Screenshots
N/A
Additional context
N/A
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: