You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Webpack but I don't process URLs. I load Bower assets from a publicly accessible folder. While things concatenated and minified from NPM are loaded through a non-publicly accessible npm_modiules folder and my build pulls out any JS that I might bundle.
I have a lot of pages that may or may not require some scripts so I deal with these dependencies on my own.
If I migrate away from Bower, am I not then forced to process URLs so that assets are correctly processed?
I also find that WebPack also causes issues when Uglify is used and that effects the way scripts have to be written and processed so it's potentially a large undertaking dealing with the older vanilla JS scripts.
The text was updated successfully, but these errors were encountered:
I use Webpack but I don't process URLs. I load Bower assets from a publicly accessible folder. While things concatenated and minified from NPM are loaded through a non-publicly accessible npm_modiules folder and my build pulls out any JS that I might bundle.
I have a lot of pages that may or may not require some scripts so I deal with these dependencies on my own.
If I migrate away from Bower, am I not then forced to process URLs so that assets are correctly processed?
I also find that WebPack also causes issues when Uglify is used and that effects the way scripts have to be written and processed so it's potentially a large undertaking dealing with the older vanilla JS scripts.
The text was updated successfully, but these errors were encountered: