-
Notifications
You must be signed in to change notification settings - Fork 40
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
all image assets start with './/' at the key of the manifest file #41
Comments
Hi, That I went for That part of the issue would belong in the Flask-Webpack repo btw. |
Oh ok, thanks for the explanation! (and the fast reply!) I would expect the assets to be like this:
rather than this:
|
Yeah, that other part of it adding |
I'm using 0.4.1 package.json:
|
I was able to resolve my issue (not the bug itself though) by adding '/' to the rootAssetPath. (I also gave the app's static folder instead of the static/images so it will include the images folder in the path, i guess this is also part of the bug, but adding the end '/' solved the issue in both cases) Used to be something like 'path/to/assets', now 'path/to/assets/' and it got rid of one '/' in the manifest for some reason. Now a manifest entry looks like: "./images/img.png":"images/img.db7c68e1892ff11bf2dff9256a8a3cd9.png", still has the './' in the beginning, but at least now i can use the url_for tag with flask_webpack. I hope this helps resolving this issue. |
I have the same issue with |
I've been using a version of your suggested webpack.config.js file you used in your flask-webpack video but for some reason this is the manifest file i'm getting ('.//' at each key and it won't add the images folder from the path, but the values are as expected):
And this is my config file:
Then i'm trying to add an asset in the html with an asset key from the manifest:
This makes the asset_url_for tag from flask_webpack not work (script and style tags are working great) because of this if in the asset_url_for function (line 123 in flask_webpack/init.py):
I'm guessing there's some logic to that if (happy to know why), so i was trying to get the plugin to output the keys correctly but with no luck. any idea why i see this issue?
Thanks,
Sarai.
The text was updated successfully, but these errors were encountered: