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
Hello, thanks for making this library! It's incredibly useful. 🙂
I noticed when I run node --inspect-brk (i.e. the Node inspector tool) in a project containing table, the Chrome DevTools complain about not being able to load source maps:
The reason seems to be that the published .js files (e.g. alignTableData.js) contain //# sourceMappingURL=<filename>.js.map at the end, but the .js.map files are not actually published.
It would be great if either 1) the .js.map files were published, or 2) the sourceMappingURL were removed, to avoid seeing a warning about missing source maps.
The text was updated successfully, but these errors were encountered:
WARNING in ./node_modules/table/dist/src/wrapString.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '/node_modules/table/src/wrapString.ts' file: Error: ENOENT: no such file or directory, open '/node_modules/table/src/wrapString.ts'
I see the same problem with React v18 (react-script v5)
Hello, thanks for making this library! It's incredibly useful. 🙂
I noticed when I run
node --inspect-brk
(i.e. the Node inspector tool) in a project containingtable
, the Chrome DevTools complain about not being able to load source maps:The reason seems to be that the published
.js
files (e.g.alignTableData.js
) contain//# sourceMappingURL=<filename>.js.map
at the end, but the.js.map
files are not actually published.It would be great if either 1) the
.js.map
files were published, or 2) thesourceMappingURL
were removed, to avoid seeing a warning about missing source maps.The text was updated successfully, but these errors were encountered: