In the 5.1.0 published package contents, all the .js files are minimized, even history.development.js. This makes inspecting or debugging the installed package difficult. (Yes, there are .map files and //# sourceMappingURL commments, but those are unlikely to make it through a bundling pipeline and asset server intact, and they don't help with inspecting the contents of node_modules/history on the filesystem.)
Only history.production.min.js should be minimized, as that is the only file that's documented for direct use in a <script> tag. Everything else will be going through a bundling pipeline, where the user will decide when and with which tool to minify. This is consistent with the practices of other prominent packages which include both *.development.js and *.production.min.js files, e.g. react.
Aside from the fact that the map files are malformed and don't work. You don't need minimized libraries. The packaging/bundler software will minimize them and create map files as needed.
In the 5.1.0 published package contents, all the .js files are minimized, even history.development.js. This makes inspecting or debugging the installed package difficult. (Yes, there are
.map
files and//# sourceMappingURL
commments, but those are unlikely to make it through a bundling pipeline and asset server intact, and they don't help with inspecting the contents ofnode_modules/history
on the filesystem.)Only history.production.min.js should be minimized, as that is the only file that's documented for direct use in a
<script>
tag. Everything else will be going through a bundling pipeline, where the user will decide when and with which tool to minify. This is consistent with the practices of other prominent packages which include both*.development.js
and*.production.min.js
files, e.g. react.