Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support for npm package manager in Kotlin/JS #4218

Merged
merged 3 commits into from
May 22, 2024

Conversation

danil-pavlov
Copy link
Contributor

No description provided.

@danil-pavlov danil-pavlov marked this pull request as ready for review May 20, 2024 12:52
@danil-pavlov danil-pavlov requested a review from a team as a code owner May 20, 2024 12:52
@danil-pavlov danil-pavlov changed the base branch from 2-0-0-doc-update to master May 21, 2024 12:32
for managing [npm](https://www.npmjs.com/) dependencies in background and can build a JavaScript bundle from a Kotlin project
typical for JavaScript development.

The plugin uses the [npm](https://www.npmjs.com/) or [Yarn](https://yarnpkg.com/) package manager
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"uses ... to download ... and can build" can be a bit confusing.

I'd alter the sentence structure to be more uniform, for example: "The plugin downloads dependencies using ... and builds JavaScript bundles from Kotlin projects using ..."

It works out of the box without additional configuration, but you can [tune it to specific needs](#yarn).

You can also use [npm](https://www.npmjs.com/) as your package manager instead. This makes the overall setup of your
project easier, as you have one less tool to manage. To use npm as your package manager, in your `gradle.properties`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From context, it's not evident to me why npm is easier and how there is one less tool to manage if we use one package manager instead of the other. Can we summarize the reasoning here?

@danil-pavlov danil-pavlov requested a review from zamulla May 22, 2024 12:52
@danil-pavlov danil-pavlov merged commit 089593b into master May 22, 2024
4 checks passed
@danil-pavlov danil-pavlov deleted the npm-package-manager branch May 22, 2024 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants