-
Notifications
You must be signed in to change notification settings - Fork 223
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
Source maps seem broken #1191
Comments
This is a huge blocker, unsure how its not a problem for more |
@dimitrisnl this issue is more about the warnings being produced, this isn't a blocker for functionality. those warnings shouldn't prevent anything from running correctly. (I'm not sure why they're being produced but just elaborating) |
I found a workaround: Add this to the webpack config: ignoreWarnings: [
/Failed to parse source map/,
], |
For me it didn't let me analyze the bundle using My workaround for that is to do The The functionality of |
I'm seeing warnings from webpack in my browser console:
The
index.mjs
file has//# sourceMappingURL=index.mjs.map
at the bottom which looks fine, however...Here are the contents of
index.mjs.map
:These reference paths like
../src/error.ts
, but there is nosrc
folder in the package as of v1.0.3, which seems to cause the warnings.The text was updated successfully, but these errors were encountered: