Open matthias-ccri opened 1 year ago
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 source-map-explorer
on a build generated by Vite.
My workaround for that is to do npx source-map-explorer ./dist/assets/*.js --no-border-checks
.
The --no-border-checks
lets me analyze the bundle again, but superstruct will appear as a black box (for me it doesn't matter).
The functionality of superstruct
itself has NOT been blocked by the warnings whatsoever, I can just ignore them.
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.