4 ms·
I'm not sure why paths are such a big issue. The config object only needs the path to your applications entry file, and the path to where to put the output. All
by manigandham 9y ago
I'm not sure why paths are such a big issue. The config object only needs the path to your applications entry file, and the path to where to put the output. All the paths within your app js (the import() statements) dont have anything to do with webpack and wouldn't run anyway if they were wrong.
What other paths are you running into problems with? Also debugging this is just like any other app, start with 1 line at a time and see what changes. You can technically run it all inside of a debugger but that's a lot of setup so the old-school 1 change at a time + console.log() statements work well. Remember its just a single-file js app that produces an object.
- myspy 9y agoThe issue is that for the result there are too many variables and unknowns that complicate the most important thing. Writing the app and not taming the build process. Take Ember for example. It lacks the freedom to configure as you please but gets you going creating very fast.
- conradfr 9y agoIt is with the paths in your styling (images, fonts) which by default are checked and rewritten during compilation (which fails if he can't find the files).