Comment by vid
I agree with sitkack. npm (packaged software) is really handle to bundle code and keep a repo up to date. But I guess if you just want a markdown editor on a page, this is fine.
I agree with sitkack. npm (packaged software) is really handle to bundle code and keep a repo up to date. But I guess if you just want a markdown editor on a page, this is fine.
It's fine that the points are different.
If you need to use npm in the rest of the project, which can be helpful for any project that uses front end Javascript, having one library (essentially) that uses a different mechanism is not great.
I have built many projects and while I swore at convoluted bundlers in the past, they are pretty nice these days.
You are arguing two (subtly) different points. Not requiring npm or any build step is great. Always.
Having it available to simplify integration into larger projects is also great.
These two things are entirely orthogonal, even if this only does the first one.