enso/lib/js/runner/package.json
Paweł Grabarz d9972d547a
Migrate to pnpm (#10422)
Fixes #10197

# Important Notes
From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 11:13:04 +00:00

36 lines
964 B
JSON

{
"name": "enso-runner",
"version": "1.0.0",
"type": "module",
"author": {
"name": "Enso Team",
"email": "contact@enso.org"
},
"homepage": "https://github.com/enso-org/enso",
"repository": {
"type": "git",
"url": "git@github.com:enso-org/enso.git"
},
"@comment scripts": {
"build": "We are using tsup to be able to generate the bundled .d.ts file. It is the only solution that works. See the following link for reference: https://github.com/Microsoft/TypeScript/issues/4433"
},
"scripts": {
"typecheck": "tsc --noEmit",
"lint": "eslint src"
},
"bugs": {
"url": "https://github.com/enso-org/enso/issues"
},
"devDependencies": {
"@types/node": "^20.11.21",
"@typescript-eslint/eslint-plugin": "^7.15.0",
"@typescript-eslint/parser": "^7.15.0",
"eslint": "^8.49.0",
"eslint-plugin-jsdoc": "^46.8.1",
"typescript": "^5.5.3"
},
"dependencies": {
"spectorjs": "^0.9.27"
}
}