Publish Library to NPM

[x80486]

I wanted to reach out regarding the publishing of the library to NPM. I'm unable to see the latest version. Are you considering to publish again to NPM?

Additionally, I noticed the project is currently using Circle CI. GitHub Actions is a built-in feature, and it works like a charm. If you are planning to migrate to GitHub Actions, I can help with that.

[janishutz]

That is the plan, but I am sadly not the maintainer, so can't publish. And yes, migrating to GH Actions was something I wanted to do but never got around to doing, so a PR with that'd be great

[henrikingo]

I can create an NPM release of course. The question is what value would it add? This is not a node / server side module, nor do we have any dependencies. Last release to NPM we got feedback that it was just for show.

[x80486]

I was under the assumption that by installing the impress.js (npm) module, it should be possible to import it to any project, rather than having to download the sources/assets from the repository.

That's the first option for me, otherwise a CDN — but these are usually blocked in many places, so it could be disappointing.

[henrikingo]

Yes, all of that is correct. I guess my question is, do people use impress.js as part of larger projects? I just use it as it is to create presentations, and I also store my presentations in a git repo.

[x80486]

The milestone will vary, so you will definitely find a multitude of approaches.

Build tools in the JavaScript land have become incredibly user-friendly, so I consistently use a build tool, regardless of the project's size. My first approach is to import from NPM; if that's not possible, then try to use a CDN, and as a last resort, I copy over the assets/sources.