Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Should Microdiff on NPM be minified? #8

AsyncBanana started this conversation in Ideas
Discussion options

In #5, @simone-sanfratello brought up minifying the code in Microdiff's NPM package. However, most people targeting the web already minify everything themselves, and many people who use Node like their dependencies being readable.
This discussion is for seeing what the community's opinions on this are. If you have an opinion on this, please react with 👍 or 👎 and add any other thoughts in the replies.

You must be logged in to vote

Replies: 2 comments 1 reply

Comment options

Just to be clear, thumbs down = should not be minified?

Any package installed from NPM should absolutely not be minified. Anyone who is interested in delivering a small app is already using a minifier for the rest of their code. Being able to read a dependency's code (preferably with comments intact) is very valuable, and it also gives cleaner error traces. Minified versions of the package can be included in the NPM distribution for those that want them, but it should not be what is used as the entry point for imports.

You must be logged in to vote
1 reply
Comment options

AsyncBanana Nov 8, 2021
Maintainer Author

Yeah, 👎 is saying it should not be minified, as Microdiff currently is

Comment options

Due to the majority that says it should not be minified, I will keep it as it is currently.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Ideas
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /