Open tjohnston-softdev opened 3 years ago
pokoli
commented
3 years ago Hi,
Thanks for sharing your work. I normally use npm publish to upload the package to npm. Is any way that can I integrate into our workflow the minified package so both packages are updated on newer releases?
tjohnston-softdev
commented
3 years ago Is any way that can I integrate into our workflow the minified package so both packages are updated on newer releases?
That is actually a good question. Compiling and releasing an updated version by hand is trivial but I'll admit it was quite tedious to manually compile the last ~40 versions. All you really have to do is copy over the .min file, copy the license, and incorporate the readme into a template that I use.
Incorporating this into the workflow would enable my package to be updated in real-time and not just whenever I have a spare moment. I can tell you're better at the DevOps stuff than I am but I'll look into it out of curiosity. I'll add you to my repo once I'm done messing around. :)
sandstrom
commented
2 years ago @pokoli I think it makes a lot more sense if papaparse is unminified. Anyone who wants minified code can do that themselves, either using any of the dozen CLI tools, or online (https://skalman.github.io/UglifyJS-online/).
Very few JS libraries these days provide pre-minified builds.
(you'll also avoid stuff like this https://github.com/mholt/PapaParse/issues/854)
I have published a separate package that only contains the minified JavaScript file. That is, without any unnecessary files such as documentation and unit tests. It is good to have those resources available but they're a complete waste of space in a production environment and inflate the package's size. This is for those who only need the minified code but still want to keep their dependencies organized.