-
-
Notifications
You must be signed in to change notification settings - Fork 226
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
ERROR in ./node_modules/json-schema-ref-parser/lib/resolvers/http.js #110
Comments
When you say that you "compile it", I'm assuming you mean that you're using a bundler like WebPack, Rollup, Browserify, etc.? In that case, be sure that you're referencing the browser module (in the |
Thanks for the quick response and yes this will help i am sure. |
Hi, I'm getting the same error. I have an Ionic 4 project (Angular) and i installed this package with 'npm i json-schema-ref-parser'. I'm getting the following error if I run 'ionic build' (ng build).
If i change the So, there might be a "package problem" but i should change things in the node_modules folder. |
I assume that Ionic uses a bundler like Webpack or Rollup or something? If so, then there should be a way to specify module substitutions. The |
Hi, under the hood, Ionic uses Angular 7 at the moment (for my project). I used json-schema-ref-parser with Ionic 3 (Angular 2/3) and it worked out of the box. So something changed... The Angular CLI uses webpack (Version: webpack 4.28.4).
|
I solved it by installing some npm browserify package and configure de tsconfig path option:
add this to tsconfig.js:
|
using version 6.0.2 and when i try to compile it give the following error even i tried all the possible solutions
Module not found: Error: Can't resolve 'http' in 'C:\Users\BitsnIO-2\testapp\node_modules\json-schema-ref-parser\lib\resolvers'
ERROR in ./node_modules/json-schema-ref-parser/lib/resolvers/http.js
Module not found: Error: Can't resolve 'https' in 'C:\Users\BitsnIO-2\testapp\node_modules\json-schema-ref-parser\lib\resolvers'
The text was updated successfully, but these errors were encountered: