A VS Code extension requires the contributions metadata to be inside `package.json` Looking at how t...

# javascript

[Edoardo Luppi]

A VS Code extension requires the contributions metadata to be inside package.json
Looking at how to customize the file, I found this: https://kotlinlang.org/docs/js-project-setup.html#package-json-customization

Being that an extension's package.json may go well beyond 1000 lines, doing it like that is extremely inconvenient impossible.
Would it be possible somehow to implement JSON "merging"?

I can probably do it myself via an additional Gradle task, but maybe it's worth a YT issue? Or was it ruled out already?

[turansky]

Looks like custom merge task is fine (best) solution

[turansky]

Which information you need from default package.json ?

[Edoardo Luppi]

@turansky only the main entry point and dependencies entries are crucial. The rest can be changed at merge time.

[turansky]

Looks like typical case for custom task

[Edoardo Luppi]

Does Gradle offers something built-in for JSON manipulation that could help here?

[turansky]

Kotlin serialization - my favourite

[turansky]

Not build-in :(

[Edoardo Luppi]

Should adding it to the buildscript classpath be sufficient?
Not sure if attaching the new task to jsPackageJson or jsPublicPackageJson

[Edoardo Luppi]

And there are also jsTestPackageJson and jsTestPublicPackageJson.
A common "entry point" would be nice

[turansky]

Custom plugin - fine entry point :)