Help with plugin development and publishing on NPM about codedoc HOT 7 CLOSED

@danielsitnik something like this?

If you need to run some tests before publishing, this might be a good example as well.

Note that these will only publish to NPM when the version specified in package.json is increased and that change is pushed to either main or master branches, but I suspect you can configure the action even further.

from codedoc.

this looks pretty strange ... will take a look over the weekend.

from codedoc.

@loreanvictor I managed to make it work!

The problem was that I was testing the package with npm link and I think somehow it messes up the module resolution.

I tried a different approach, doing npm pack and then npm install pointing directly to the generated tgz file, and this did the trick!

The plugin has been published to NPM and is ready to use!
https://www.npmjs.com/package/codedoc-mermaid-plugin

from codedoc.

Ahhh yes yes! There are some Github actions for publishing to NPM.
I did add one but it was being triggered on new releases, I just need to tweak it to publish when I merge to the main branch.

from codedoc.

Have you automated this process? Is so, I would to look at it.

from codedoc.

Have you automated this process? Is so, I would to look at it.

Which process do you mean?

from codedoc.

I mean the process of publishing the NPM package.

For example, I am the maintainer of Elmish.WPF. To publish a new NuGet package, I follow these steps. Essentially, I change the version and push to master. Then this workflow creates a NuGet package with that version and publishes it to nuget.org.

Do you have a GitHub workflow that automatically publishes a new NPM package for you?

from codedoc.