-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.bundle.rxjs is failing #2105
Comments
I have the same issue. |
Have the same issue. can confirm that removing the ^ solved the issue |
Fix is pushed to master. |
Commit fixes the post-install hook but prod builds still failing for me. Specifically, it throws the same error on one of my required modules that requires rxjs. |
This might be related to this problem: ReactiveX/rxjs#2971. Hoping for a fix in RxJS 5.5.1. For now use @ogousa's advice and roll back to RxJS 5.4.3. |
Yeah that’s what I ended up doing. Thanks. |
btw, I get the @mgechev 's fix and it works in dev and prod mode for me. |
I'm submitting a ... (check one with "x")
Current behavior
Currently I'm getting the below error at build.bundle.rxjs with latest angular-seed
'build.bundle.rxjs' errored after 562 ms
Error on fetch for rxjs/operators at file:///clientdata/work/cm/src/angular/node_modules/rxjs/operators.js
Loading rxjs/Rx
Error: ENOENT: no such file or directory, open '/clientdata/work/cm/src/angular/node_modules/rxjs/operators.js'
Expected behavior
build.bundle.rxjs should work without errors.
Minimal reproduction of the problem with instructions
I tried..
npm cache clean
rm -rf node_modules
npm install
then I got above errors.
I think rxjs.5.5x. causing this issue. I downgraded to rxjs.5.4.x then working fine.
What is the motivation / use case for changing the behavior?
N/A
Please tell us about your environment:
Operating System: Red Hat Enterprise Linux Server 7.2 (Maipo)
CPE OS Name: cpe:/o:redhat:enterprise_linux:7.2:GA:server
Kernel: Linux 3.10.0-327.28.3.el7.x86_64
Architecture: x86-64
Angular Seed Version:
aaaaf75
ab4a987
Node:
node --version
=v7.9.0
The text was updated successfully, but these errors were encountered: