Use a npm release process?

[davidlehn]

It's unclear what the release process is for this package. Looks like it has been a branch per version, and built js files are committed in dist, then the branch is tagged?

Would it make sense to use a build process that publishes to npm? Then adjust to use jsdelivr npm links. It would be similar but avoid having build artifacts accumulate in dist/*.js in git.

[OR13]

@iherman @pchampin does W3C have an npm account?

[iherman]

@iherman @pchampin does W3C have an npm account?

I do not know. @deniak @plehegar ?

[deniak]

@iherman @pchampin does W3C have an npm account?

I do not know. @deniak @plehegar ?

We do: https://www.npmjs.com/org/w3c

Let me know who should be invited.

[davidlehn]

@deniak We're working on how to deploy now. If access policies allow it, I could do npm releases. I'm @davidlehn on npm too.
https://www.npmjs.com/~davidlehn

[deniak]

@davidlehn, I just sent you the invite.

[iherman]

@deniak, can I be added on the list for npm publishing? @davidlehn, if that is good, then I can be a fall back, see #37 (comment).

@deniak, how does that work exactly. I do submit packages to npm time-to-time, but from my own repositories. Will npm just "know"?

[deniak]

@iherman I just sent you the invite.
I've never publish a npm package under a different account but it looks like you need to add w3c as the owner of the package: https://docs.npmjs.com/cli/v7/commands/npm-owner

[iherman]

@iherman I just sent you the invite.

Thank you, have just accepted it.

I've never publish a npm package under a different account but it looks like you need to add w3c as the owner of the package: https://docs.npmjs.com/cli/v7/commands/npm-owner

@davidlehn I presume you know this. Is it so that you have to add me as an owner to the package via npm? This is how I read the reference of @deniak ...