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'm attempting to insert my pkg.version into the modulePath (to avoid caching), but the package name just keeps defaulting to the 'data-main' of the original script tag.
This code worked before (about 2 months ago), but has broken since I last tried it, I assume due to 78a3ec5 - it looks like 'file.modulePath' isn't returning anything (line 42 of replace.js).
Oddly, the file is named correctly - it's just the script tags that aren't updated properly.
Thanks for the detailed report. Do you think you could be coming up with a PR & in case you're not able to, at least a failing unit test so that someone else is able to tackle the issue?!
Can someone please confirm if the issue persists in current master.
There was some issue with use of modulePath in 78a3ec5 but that was fixed in 940e41d
I'm attempting to insert my pkg.version into the modulePath (to avoid caching), but the package name just keeps defaulting to the 'data-main' of the original script tag.
This code worked before (about 2 months ago), but has broken since I last tried it, I assume due to 78a3ec5 - it looks like 'file.modulePath' isn't returning anything (line 42 of replace.js).
Oddly, the file is named correctly - it's just the script tags that aren't updated properly.
The text was updated successfully, but these errors were encountered: