-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Minified Package (papaparse-min) #897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, Thanks for sharing your work. I normally use |
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 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. :) |
@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 #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.
The text was updated successfully, but these errors were encountered: