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.
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
.jsfiles (e.g.alignTableData.js) contain//# sourceMappingURL=<filename>.js.mapat the end, but the.js.mapfiles are not actually published.It would be great if either 1) the
.js.mapfiles were published, or 2) thesourceMappingURLwere removed, to avoid seeing a warning about missing source maps.