-
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
Cannot use esbuild builder after 17.0.X with Bazel #27556
Comments
The last version this works was 17.0.3. From 17.0.4 onward this happens, specifically from 0634a4e onward. From what I can tell, this is caused the build escaping the sandbox. I believe this has to do with the way Edit: Disregard the patch I added here earlier, I believe that only makes it worse. |
Would it be possible to try the latest v18 release candidate to see if this resolves the problem (currently v18.0.0-rc.2)? |
I gave it a quick try and it doesn't resolve the problem. |
I used the 'browser-esbuild' since the 'application' doesn't seem to exist anymore. |
Which @angular/* package(s) are the source of the bug?
bazel, compiler-cli, compiler
Is this a regression?
Yes
Description
Hi, not sure if this is the right place for this.
Basically calling the architect bin with bazel.
It was working fine when updating to 17.0
But since I updated to to 17.1+ there are issues with esbuild
First was main.ts not bein available in the ts compilation (fixed with "preserveSymslinks" :true)
Second is @angular/material cannot be resolved with its path
Repro with 17.0.1
Repro with 17.3.4
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?
It still compiles correctly with the regular "browser" builder.
The text was updated successfully, but these errors were encountered: