-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Can't resolve 'stream' #524
Comments
I resolved that issue by adding the library to the tsconfig.ts like this:
|
I think that I think it's better to:
|
@jmandreslopez Not works for me. |
Thanks @jmandreslopez I did work |
I think you're incorrect. That solution will tell every module in your app to load @jmandreslopez's solution is, in general, the superior solution for most apps because it only affects how the I'll also note that both solutions show the path prefixed with |
See also #477 which might be the same issue --- tl;dr: probably not an issue, just a misleading cosmetic warning. |
When webpack/rollup or another bundler, implementing the [`browser-resolve`](https://www.npmjs.com/package/browser-resolve) spec tries to resolve `jszip` for a browser-based project they fail with: ``` ERROR in ./node_modules/jszip/lib/readable-stream-browser.js Module not found: Error: Can't resolve 'stream' in '/node_modules/jszip/lib' ``` Since you already produce a browser build, we just need to point to it inside of `package.json`'s `browser` field. PS: You'd probably want to double check the semantics of `"."`. Looking at `browser-resolve` it seems that everything will work as expected. Also, trying empirically with webpack, everything worked out, but few more pairs of eyes would be greatly appreciated. Also @sokra should be able to share a valuable opinion. Fix Stuk#524 Fix Stuk#521 Fix Stuk#477
Hello. After updating the version of Angular to 6.0 I got the next error.
The text was updated successfully, but these errors were encountered: