Bradleycorn
05/13/2021, 7:51 PMpackage.json
files have a few problems:
1. they have dependencies with “hardcoded” absolute file paths, like: "kotlin": "file:/Users/brad.ball/dev/multiplatform/new/wager-utils/build/js/packages_imported/kotlin/1.5.0",
2. the dependencies list contains entries for kotlin-test-js-runner
and kotlin-test
. Why would those be dependencies for a published package? Seems like at best they should be devDependencies.
With the hard coded file paths, you can’t really publish the package or use it anywhere but on the machine where it was generated…
The full package.json output is included in the replies thread…
Am I doing something wrong? I have a pretty standard gradle config, haven’t really changed much from what was produced by IntelliJ when creating the project.Bradleycorn
05/13/2021, 7:52 PM{
"name": "wager-utils",
"version": "1.1.6",
"main": "kotlin/wager-utils.js",
"devDependencies": {},
"dependencies": {
"kotlin": "file:/Users/brad.ball/dev/multiplatform/new/wager-utils/build/js/packages_imported/kotlin/1.5.0",
"kotlin-test-js-runner": "file:/Users/brad.ball/dev/multiplatform/new/wager-utils/build/js/packages_imported/kotlin-test-js-runner/1.5.0",
"kotlin-test": "file:/Users/brad.ball/dev/multiplatform/new/wager-utils/build/js/packages_imported/kotlin-test/1.5.0"
},
"peerDependencies": {},
"optionalDependencies": {},
"bundledDependencies": []
}