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
building failed sometimes with Can't find stylesheet to import #27167
Comments
This appears to be a package manager related issue. The Angular CLI does not control the layout or content of installed packages. Does the issue occur if another package manager is used? |
We never tried I want to add we upgrade from yarn 1.x to 4.0.2, and the issue still exists |
@clydin Could you elaborate on how this is a package manager issue? |
hi @clydin
this is my build script, it fails now then on retry 1 or 2 times it passes |
Unfortunately without a reproduction it's hard to debug and understand what is the problem here. |
how can I reproduce it if it happens 5% of the times? |
The same problem sometimes occurs in my GitLab pipeline, approximately 1% of the time. |
We have the same problem. Same as #25018 and #26389. We are also getting this issue here:
We've tried both to point This never happens in local, only in CI. It seems that the problem might be related to the typography partials? I saw some suggesting to make a local copy of whatever typography function you need in your styles, but I feel it's highly impractical, both for the daisy-chain effect of functions you would have to copy, and also in terms of maintainability. |
Command
build
Is this a regression?
The previous version in which this bug was not present was
No response
Description
about 5% of our pipeline fail with this error
it happened only one with
ng serve
and it was very difficult to resolve, my colleague had to uninstall node and install it againpreviously he tried to delete the project and clone it again, remove yarn cache but neither work
Minimal Reproduction
it's impossible to reproduce, since even rerunning the same one succeed
it's not code error
this happens even when we were using webpack (we are using the application builder which uses esbuild), I noticed it in versions 15 and 17 of Angular
Exception or Error
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: