Good morning everyone :sunny: I need your input s...

# javascript

[Artem Kobzar]

Good morning everyone ☀️

I need your input so much in the following question.
In the thread, please share how you publish Kotlin/JS artifacts (not KLIB, but the executable) to a registry (e.g., NPM, JSR, Maven) and any pain points you've encountered with the approach.
Thank you for the help 🙏

Artem, Kotlin/JS Lead

[andylamax]

I use the #C01LQTET9P1 plugin to publish to an internal Vedaccio instance

[Edoardo Luppi]

npm-publish is the way for us. We publish to internal npm repositories under Nexus.
We're using the active fork at https://github.com/DanySK/npm-publish.

[Edoardo Luppi]

And no issues I'd say. The only small problem I had was the missing package type.
You can see what I mean here.

Edit: forgot https://github.com/DanySK/npm-publish/issues/23, but it's workaroundable.

[Luv Kumar]

we use npm-publish and publish to github npm registry

[Rob Murdock]

I've been using command line commands in simple gradle tasks, - "npm publish", basically.

Most of the pain points I recall being very simple - ensuring all the right package.json things are in place, or getting the intended name.

If i was publishing libraries to be consumed that way, I'd probably have some complaints about how modularization works, but since i'm publishing CLI tools that hasn't mattered at all.

[Artem Kobzar]

@Rob Murdock, and why did you decide to use custom tasks and not #C01LQTET9P1?

[Rob Murdock]

truly I don't know that it was a deeply considered decision, so much as it worked quickly and hasn't needed to change since!

[Kents]

Planning to share artifacts on AWS CodeArtifact but haven't gotten to that point in our SDK development yet.

[Edoardo Luppi]

@Artem Kobzar I've seen the npm-publish plugin has been moved under the Kotlin org. Is there a plan to transition maintenance under the JetBrains/Kotlin umbrella?

[Artem Kobzar]

Exactly, this is our plan!
Currently, I'm setting up all the required work and agreements, but yes, we've contacted @Big Chungus and agreed on our maintenance of his fantastical plugin.
As soon as I finish all the work and publish the plugin, I will make an official announcement in #C0BJ0GTE2 and #C01LQTET9P1

[Kents]

What an amazing user handle and news!

[andylamax]

This is every open source contributor news. Big up to @Big Chungus

I am proud to be one of the contributors (however minor my contribution was) of this amazing plugin

[Artem Kobzar]

And yes, the plugin remains open source, so contributions are welcome!
I also want to cherry-pick all the changes @Danilo Pianini made to his fork.

[Edoardo Luppi]

Yeah was just going to mention that there are some commits related to Gradle compatibility in his fork

[Artem Kobzar]

Actually, I really would appreciate it if someone could help me with the picking up the changes (because after a vacation, I'm a bit overloaded with tasks 😅)

[Big Chungus]

Should be able to just create a pr from fork into base. I don't expect there to be any commits in base that are not in the fork

[Edoardo Luppi]

If no one offers for that, I can diff the fork by end of week and open a PR with cherry picked commits.
But yeah as @Big Chungus said it should be fairly straightforward, apart from the different artifact coordinates.

[Edoardo Luppi]

I took a look at how easy it is to cherry pick stuff.
It's not as straightforward as I would have expected, in the sense that there were quite a lot of infra changes, especially to get rid of Git submodules.