-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative path showing up in asset map? #29
Comments
@ArnaudRinquin and @gregersrygg both worked on the |
A long time since I worked on this, so I don't remember much. @rebolyte Have you tried outputting the |
Thanks to all contributors to this project, it has been very helpful on my journey to replace gulp with npm scripts, which originated from this blog post: https://www.keithcirkel.co.uk/how-to-use-npm-as-a-build-tool/. I too was having issues with the pathing in the asset map file and could never get it to do exactly what I needed. Turns out, I could get exactly what I wanted without even using this package. Basically, my needs were as follows:
I was able to accomplish this using the following in my npm scripts:
Hopefully this helps someone! |
First off, this lib is exactly what I was looking for. Thanks for making it!
I am having an issue with a relative path showing up in the assets JSON file. Basically, I need the entry in the asset map to have a slightly different path from where the file gets output. I need the path to be stored as "js/bundle.{hash}.js" but the file output to "static/js/bundle.{hash}.js". This seems to be exactly what the
--cwd
option does, and it almost works, but then it creates an entry in the asset map like so:I don't want the leading
../
on the filename. Where is it coming from? I could go through and strip it off after every build, but that seems hacky.Here's the NPM script that I'm using:
Ideas? Let me know if you need any other info.
The text was updated successfully, but these errors were encountered: