3 ms·
Looking at this now. Thanks! How about a dist folder with a plain js file (or a js file and a css file) that you can load directly? I am sick unto death of No
by Turing_Machine 3y ago
Looking at this now. Thanks!
How about a dist folder with a plain js file (or a js file and a css file) that you can load directly?
I am sick unto death of Node and all its associates.
- kermire 3y agoNot as extensive as the previous poster. I wrote a small custom component wrapper a while back: https://github.com/flawiddsouza/code-mirror-custom-element https://github.com/flawiddsouza/code-mirror-custom-element.
- spankalee 3y agoThe npm package has the pre-built files: https://www.npmjs.com/package/codemirror-elements https://www.npmjs.com/package/codemirror-elements I publish to npm because 1) Package managers are a fabulous idea. They're an easy way to download a package and it's dependencies, and update them over time. 2) it's not a good idea to push build artifacts to your repo, 3) This depends on CodeMirror, which is published to npm. Otherwise I would have to provide it too. That's too much work. 4) you don't need to be a Node developer to use npm.