-
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
TypeError: Cannot read property 'apply' of undefined in CachedInputFileSystem.js #9561
Comments
I'm having the same problem with the latest version of the Angular CLI (1.6.8). I've resolved this by temporarily setting the Angular CLI version in my package.json to 1.6.7 |
Yep. Same. |
Thanks @TheOriginalJosh , that helped for now! |
Hmm odd.. I seemed to have the same issue. but then it was suddenly gone... Can't say that I did any changes other than trying to revert stuff to older versions and then resat it back to where it all started. |
Pinning to 1.6.7 addressed the issue for now. |
I experienced this issue briefly while still on 1.6.6, and like everyone else it went away on it's own. |
Looks like it was an issue with copy-webpack-plugin@4.4.0. Once it started working again it installed 4.4.1 which fixed this issue. |
Closing this as fixed in copy-webpack-plugin. Please update your node_modules folder and you should be good to go. |
@TheOriginalJosh 95% emittingX:\NewClalWeb\base-project\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:70
|
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. |
Versions
Repro steps
Running ng server or ng build on the project
Use the repository from here:
https://github.com/tsimon-edu-sharing/cli-sample
Observed behavior
Desired behavior
Should run / build, or give a more useful error
Mention any other details that might be useful (optional)
Reason seems to have something to do with including the font stylesheet via the angular-cli.json
The text was updated successfully, but these errors were encountered: