Conversation
|
|
||
| > To configure this, you can also use [Gradle properties](https://docs.gradle.org/current/userguide/build_environment.html). | ||
| > | ||
| {style="tip"} |
There was a problem hiding this comment.
Is this important to note? Is it more common knowledge that we should remind people of, or rather a counterintuitive thing that people are generally not aware of?
Also I'm not entirely sure what this tip refers to — the entire npmPublish {} block?
There was a problem hiding this comment.
We could skip it (I also don't understand what I referred here)
| * The `registries`, which specify to which registry the library is going to be published. | ||
| * The `organization`, `packageName` (by default, the name of the module is taken), and `version` (by default, the version specified in the module is taken) of your library. | ||
| * The `license`, under which your library is published. | ||
| * The `author`, which specifies the author of the library (you can also add `contributors`). |
There was a problem hiding this comment.
I'm not sure it's obvious how to map the contributors array to the Gradle script. Should we add an example for this?
| @@ -0,0 +1,246 @@ | |||
| [//]: # (title: Publish your library to NPM – tutorial) | |||
There was a problem hiding this comment.
I have a hard time with library / package here: can we settle on "library" when referring to the actual KMP project and "package" when it's about the npm package being described and published? I think people mapping npm docs onto our tutorial will have an easier time.
There was a problem hiding this comment.
Maybe project would be easier in this case? package word has also a clash in terminology in Kotlin/Java world
3 participants
A guide on publish Kotlin web library to NPM