Closed don-bluelinegrid closed 7 years ago
Your code seems to be requiring .ts
source files instead of .js
modules from within 'node_modules'. Not sure what's causing that, but my best guess is ts-node
.
@niieani
I understand why you may say that, based on the error I pasted. However, if that was the case, then the entire webpack-typescript skeleton couldn't work, right? But, it does work, and it uses the .js files in the /node_modules directory.
If I remove the Resolve plugin, then things work. So, it does seem specific to using the plugin with the typescript-webpack skeleton, which is what introduced ts-node. Have you tested with that? Again, my project is directly based on the latest webpack-typescript skeleton, with minimal changes.
Thanks, Don
@niieani
Also, it is not "your code" (mine) that is requiring the .ts source files -
[at-loader] node_modules/webpack-dependency-suite/plugins/root-most-resolve-plugin.ts:1:1
No, at-loader
is the default name of the awesome-typescript-loader
. Seems it's trying to validate too much. Try adding exclude: ["node_modules"]
to your tsconfig.json
.
@niieani
Again, just to clarify - I've not previously had any issue with typescript loading or ts-node. Only now, when I try to use this dependency plugin. So, what is making it seem that all of the node-modules needs to be excluded, when this has never previously been a problem?
Don
Hi @don-bluelinegrid. Sorry for the late reply. Please check out the new aurelia webpack plugin, which does not require this set of plugins.
@niieani
Bazyli,
I am trying to use your dependency plugin, to resolve this issue:
https://github.com/aurelia/webpack-plugin/issues/44#issuecomment-282843031
I am getting these errors after adding the RootMostResolve plugin:
Do you have any advice?
I'm attaching my webpack config, which is a very slightly modified version of the webpack-typescript skeleton config.
Thanks, Don