-
Notifications
You must be signed in to change notification settings - Fork 12
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 is wrong when fileName contains a directory #14
Comments
coder-layne
added a commit
that referenced
this issue
Aug 10, 2023
…path of the importer during writeBundle #14
coder-layne
added a commit
that referenced
this issue
Aug 10, 2023
…path of the importer during writeBundle #14
coder-layne
added a commit
that referenced
this issue
Aug 10, 2023
…path of the importer during writeBundle #14
Thank you for your feedback. The plugin will adjust the extracted resource's address according to the importer's output path from v0.4.2. |
I just tried 0.4.3 and it works. Thank you very much. For me this issue can be closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you so much for creating this plugin.
I create two different output directories for the different two formats es and cjs. I got the idea from
https://www.sensedeep.com/blog/posts/2021/how-to-create-single-source-npm-module.html
This is the config I am using right now:
Sadly the asset path is kept at
./assets
in the index.js files. I now added a build step that copies the assets into the mjs and cjs directories. Is there any chance that you might be able to change the imports to../assets
instead?The text was updated successfully, but these errors were encountered: