Webpack Compilation error #173

Activity

1. ChrisProlls commented on Jul 12, 2017

   

   ChrisProlls

   on Jul 12, 2017

   More actions

   Same as me, any ideas ?
2. ordinaryorange commented on Jul 24, 2017

   

   ordinaryorange

   on Jul 24, 2017

   More actions

   I had the same error, but was able to remove the package depending on source-map-support, which then got rid of it. @smile18 If you cant remove bunyan what happens if you add the source-map-support package ?
3. bzalasky commented on Aug 2, 2017

   

   bzalasky

   on Aug 2, 2017

   More actions

   It appears to be caused by these lines (~470 in source-map-support.js)...

   if (options.hookRequire && !isInBrowser()) {
       var Module;
       try {
           Module = require('module');
       } catch (err) {
       // NOP: Loading in catch block to convert webpack error to warning.
       ...
   }
   

   Perhaps webpack 2 is treating this differently than webpack 1 did?
4. jscinoz commented on Oct 27, 2017

   

   jscinoz

   on Oct 27, 2017

   Last edited by jscinoz

   More actions

   Webpack 2/3 will attempt to parse any and all ES dynamic import() / CommonJS require() calls present in input files. When the Webpack build is has target: web, neither module nor fs will be available, hence the require calls for each of these will fail to resolve and Webpack will fail the build.

   To work around this, you can set node.fs and node.module both to "empty" in your Webpack configuration, e.g:

   {
     /* Other configuration keys */
     node: {
       fs: "empty",
       module: "empty",
     }
   }
5. Ventzy commented on Jan 28, 2018

   

   Ventzy

   on Jan 28, 2018

   More actions

   Any idea how to do that in angular-cli (without ng eject)?
6. raed667 commented on Feb 21, 2018

   

   raed667

   on Feb 21, 2018

   More actions

   up?
7. ramiy commented on Dec 16, 2018

   

   ramiy

   on Dec 16, 2018

   More actions

   Had the same issue:

   warning  in ./node_modules/vue-monaco/node_modules/monaco-editor/esm/vs/editor/common/services/editorSimpleWorker.js
   
   Critical dependency: the request of a dependency is an expression
   
   
   warning  in ./node_modules/source-map-support/source-map-support.js
   
   Module not found: Error: Can't resolve 'module' in '.\node_modules\source-map-support'
   

   Solved with Webpack configure mentioned above:

   node: {
     fs: 'empty',
     module: 'empty',
   },
   

   Thanks @jscinoz !!!
8. JSONRice commented on May 7, 2019

   

   JSONRice

   on May 7, 2019

   More actions

   Yeah this is an issue for me as well. Please fix your software @evanw
9. LinusU commented on May 8, 2019

   

   LinusU

   on May 8, 2019

   Collaborator

   More actions

   Please fix your software

   Would be happy to accept a pull request to fix this @Jasonwr ☺️
10. JSONRice commented on May 8, 2019

    

    JSONRice

    on May 8, 2019

    More actions

    @LinusU I'm strapped for time at the moment. Lots of coding these days. Also I'd have to ramp up on the internals of this package before being able to submit a defect free PR.