variablelab/theatre
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
theatre/package.json

53 lines
1.5 KiB
JSON
Raw Normal View History

Initial OSS commit
2021-06-18 13:05:06 +02:00
{
"name": "theatre-monorepo",
"license": "Apache-2.0",
0.4.0-dev.18
2021-09-13 19:17:34 +02:00
"version": "0.4.0-dev.18",
Initial OSS commit
2021-06-18 13:05:06 +02:00
"workspaces": [
"packages/*",
Moved examples to a separate folder
2021-08-06 12:00:19 +02:00
"examples/*",
Initial OSS commit
2021-06-18 13:05:06 +02:00
"theatre"
],
"scripts": {
WIP: Getting r3f to work with create-react-app * Temporarily disabled ESM bundles because the current setup confuses webpack4 (but not parceljs). Since create-react-app uses webpack4, not doing this would make theatre incompatible with CRA.
2021-08-07 21:41:07 +02:00
"playground": "yarn workspace playground run serve",
Initial OSS commit
2021-06-18 13:05:06 +02:00
"typecheck": "tsc --build ./devEnv/typecheck-all-projects/tsconfig.all.json",
"test": "jest",
"postinstall": "husky install",
Simplified the deployment script * Implemented yarn run deploy, which deploys all packages to npm, with the same version assigned to all of them.
2021-08-04 21:51:25 +02:00
"deploy": "zx devEnv/deploy.mjs",
Removed the automatically generated docs I tried to generate the API section of the docs automatically from tsdoc comments. That failed for the follwing reasons: 1. It has been difficult to configure the layout of the API docs, such as, what information to show, how to sort the information, etc. I kept getting less relevant parts of the API show up before the more important parts. I would have had to write a plugin/theme for typedoc to fix that, which doesn't seem worth the effort. 2. The generated docs don't seem to be nearly as useful as the docs shown in the editor. It's just easier to browse the API in an IDE than on a static website. 3. Docs must have a narrative (we're trying to walk the user through the library) which goes against the unordered nature of automatically generated docs.
2021-09-05 13:51:42 +02:00
"lint:all": "eslint . --ext ts,tsx --ignore-path=.gitignore --rulesdir ./devEnv/eslint/rules"
Initial OSS commit
2021-06-18 13:05:06 +02:00
},
"lint-staged": {
"**/*.(t|j)s?(x)": [
"eslint --rulesdir ./devEnv/eslint/rules --fix",
"prettier --write"
]
},
"devDependencies": {
Upgrade deps
2021-09-01 10:41:54 +02:00
"@babel/core": "^7.15.0",
"@babel/plugin-proposal-class-properties": "^7.14.5",
"@babel/plugin-proposal-nullish-coalescing-operator": "^7.14.5",
"@babel/plugin-proposal-optional-chaining": "^7.14.5",
"@babel/preset-env": "^7.15.0",
"@babel/preset-react": "^7.14.5",
"@babel/preset-typescript": "^7.15.0",
"@typescript-eslint/eslint-plugin": "^4.30.0",
"@typescript-eslint/parser": "^4.30.0",
"esbuild": "^0.12.24",
Initial OSS commit
2021-06-18 13:05:06 +02:00
"esbuild-jest": "^0.5.0",
Progress with cra
2021-08-07 22:30:29 +02:00
"eslint": "^7.32.0",
Initial OSS commit
2021-06-18 13:05:06 +02:00
"eslint-plugin-jsx-a11y": "^6.4.1",
Upgrade deps
2021-09-01 10:41:54 +02:00
"eslint-plugin-react": "^7.25.1",
Initial OSS commit
2021-06-18 13:05:06 +02:00
"eslint-plugin-react-hooks": "^4.2.0",
Upgrade deps
2021-09-01 10:41:54 +02:00
"eslint-plugin-unused-imports": "^1.1.4",
Initial OSS commit
2021-06-18 13:05:06 +02:00
"husky": "^6.0.0",
Upgrade deps
2021-09-01 10:41:54 +02:00
"jest": "^27.1.0",
Initial OSS commit
2021-06-18 13:05:06 +02:00
"lerna": "^4.0.0",
Upgrade deps
2021-09-01 10:41:54 +02:00
"lint-staged": "^11.1.2",
"prettier": "^2.3.2",
"typescript": "^4.4.2",
Simplified the deployment script * Implemented yarn run deploy, which deploys all packages to npm, with the same version assigned to all of them.
2021-08-04 21:51:25 +02:00
"zx": "^2.0.0"
Initial OSS commit
2021-06-18 13:05:06 +02:00
},
"dependencies": {
Removed the automatically generated docs I tried to generate the API section of the docs automatically from tsdoc comments. That failed for the follwing reasons: 1. It has been difficult to configure the layout of the API docs, such as, what information to show, how to sort the information, etc. I kept getting less relevant parts of the API show up before the more important parts. I would have had to write a plugin/theme for typedoc to fix that, which doesn't seem worth the effort. 2. The generated docs don't seem to be nearly as useful as the docs shown in the editor. It's just easier to browse the API in an IDE than on a static website. 3. Docs must have a narrative (we're trying to walk the user through the library) which goes against the unordered nature of automatically generated docs.
2021-09-05 13:51:42 +02:00
"node-gyp": "^8.1.0"
Initial OSS commit
2021-06-18 13:05:06 +02:00
}
Added prettier to yarn deploy
2021-08-06 11:44:20 +02:00
}
Reference in a new issue Copy permalink