I am using typescript client side in a project managed using web pack.
When web pack processes typescriptServices.js, some part of the getNodeSystem code is evaluated because (typeof module !== "undefined" && module.exports) is true.
Evaluating the code, web pack finds some references to require calls and try to find modules, it fails to do so because I don't use node modules client side.
Is there a way for you to get rid of this problem ? Perhaps it is possible to split the library depending on if it is used client or server side ?
I am using typescript client side in a project managed using web pack.
When web pack processes typescriptServices.js, some part of the getNodeSystem code is evaluated because (typeof module !== "undefined" && module.exports) is true.
Evaluating the code, web pack finds some references to require calls and try to find modules, it fails to do so because I don't use node modules client side.
Is there a way for you to get rid of this problem ? Perhaps it is possible to split the library depending on if it is used client or server side ?