scratchfoundation/scratch-vm
1
0
Fork 0
mirror of https://github.com/scratchfoundation/scratch-vm.git synced 2024-12-23 06:23:37 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
scratch-vm/package.json

109 lines
3.7 KiB
JSON
Raw Normal View History

Initial commit
2016-03-28 12:53:44 -04:00
{
Initial commit
2016-04-08 13:10:37 -04:00
"name": "scratch-vm",
chore(release): 1.3.23 [skip ci] ## [1.3.23](https://github.com/LLK/scratch-vm/compare/v1.3.22...v1.3.23) (2023-01-23) ### Bug Fixes * **deps:** update dependency scratch-l10n to v3.15.20230123032119 ([01073df](https://github.com/LLK/scratch-vm/commit/01073df62b9fd6d40fd82012e79b3f2442c0762d))
2023-01-23 02:56:39 -05:00
"version": "1.3.23",
WIP
2016-04-18 17:20:30 -04:00
"description": "Virtual Machine for Scratch 3.0",
Initial commit
2016-03-28 12:53:44 -04:00
"author": "Massachusetts Institute of Technology",
"license": "BSD-3-Clause",
Initial commit
2016-04-08 13:10:37 -04:00
"homepage": "https://github.com/LLK/scratch-vm#readme",
Initial commit
2016-03-28 12:53:44 -04:00
"repository": {
"type": "git",
chore(release): 1.1.7 [skip ci] ## [1.1.7](https://github.com/LLK/scratch-vm/compare/v1.1.6...v1.1.7) (2022-08-31) ### Bug Fixes * **deps:** update dependency scratch-semantic-release-config to v1.0.4 ([e57d1d5](https://github.com/LLK/scratch-vm/commit/e57d1d5da5185458ab97913bfe840540473ff850))
2022-08-31 17:57:30 -04:00
"url": "https://github.com/LLK/scratch-vm.git",
chore(release): 1.3.23 [skip ci] ## [1.3.23](https://github.com/LLK/scratch-vm/compare/v1.3.22...v1.3.23) (2023-01-23) ### Bug Fixes * **deps:** update dependency scratch-l10n to v3.15.20230123032119 ([01073df](https://github.com/LLK/scratch-vm/commit/01073df62b9fd6d40fd82012e79b3f2442c0762d))
2023-01-23 02:56:39 -05:00
"sha": "0c0cb1221e63425a2921cb0b3e9313acd65009da"
Initial commit
2016-03-28 12:53:44 -04:00
},
Move build outputs into a `dist/` subdirectory (#375) * Move Node output: /dist.js => /dist/node/scratch-vm.js * Move web output: /vm{.js,.min.js} => /dist/web/scratch-vm{.js,.min.js} * Update build output references in package.json and the playground's index.html * Move the VirtualMachine class out of index.js into its own file, referenced by index.js. The VirtualMachine class is otherwise unchanged. * Add .gitattributes rules for new file types which were added to this repository without specifying their text/binary attributes * Turn on source maps in webpack and add corresponding .gitignore rule
2017-01-13 16:34:26 -05:00
"main": "./dist/node/scratch-vm.js",
Use src/index as browser entry point Use src/index.js as the entry by default in tools building scratch-vm into a larger package. This saves file space by excluding extra webpack boilerplate and may allow for deeper optimizations. Depend on script dependencies for downstream webpack. For another package to build in scratch-vm's dependencies without them already being built into a consumed webpack build they need to be listed as dependencies. This can benefit large projects that reuse the same dependencies multiple times. Node will still use the main entry point and its webpack build leaves the dependencies as external references so it may reuse common modules in Node as well as in a build a browser environment.
2018-04-30 11:53:01 -04:00
"browser": "./src/index.js",
Initial commit
2016-03-28 12:53:44 -04:00
"scripts": {
Add jsdoc to package json and test/build tasks
2018-07-31 09:00:19 -04:00
"build": "npm run docs && webpack --progress --colors --bail",
Use unqualified paths in package.json scripts This allows stuff like yarn workspaces to function with node_modules hoisted.
2017-09-22 05:41:08 -04:00
"coverage": "tap ./test/{unit,integration}/*.js --coverage --coverage-report=lcov",
ci: add GH Pages deploy and the i18n cron job All non-cron builds deploy to GH Pages, but only release branches generate actual releases on npm / GH. Hotfix branches are considered release branches and should be released under the `hotfix` tag on npm.
2022-06-06 20:08:30 -04:00
"deploy": "touch playground/.nojekyll && gh-pages -t -d playground -m \"Build for $(git log -n1 --pretty=format:\"%h %s\") [skip ci]\"",
Add jsdoc to package json and test/build tasks
2018-07-31 09:00:19 -04:00
"docs": "jsdoc -c .jsdoc.json",
Add scratch-l10n dependency (#1799) * update scratch-l10n dependency The new scratch-l10n package includes a script that will push the source file to transfex. Updated the package.json to push the source after extracting strings. Travis deploy that will build and push strings if run as a cron job * Fix package-lock Ran `npm i` as suggested by failing travis log.
2018-12-03 14:24:00 -05:00
"i18n:src": "mkdirp translations/core && format-message extract --out-file translations/core/en.json src/extensions/**/index.js",
"i18n:push": "tx-push-src scratch-editor extensions translations/core/en.json",
Preliminary localization (#777) * localize the block and menu strings in the pen extension * adds .tx/config to be able to push translations to transifex * includes format-message to localize strings and extracting them. * add setLocale function to VM to allow GUI to pass in locale data. * refresh block definitions when the locale changes. ### Still to be decided For now just extracting messages from the pen extension into their own file. We’ll need to decide if each category gets its own file, or group all the strings into one resource.
2017-12-11 15:41:45 -05:00
"lint": "eslint . && format-message lint src/**/*.js",
chore: add husky hook for commitlint
2022-06-02 13:14:41 -04:00
"prepare": "husky install",
Don't run prepublish on install
2017-05-13 20:25:34 -04:00
"prepublish": "in-publish && npm run build || not-in-publish",
Use unqualified paths in package.json scripts This allows stuff like yarn workspaces to function with node_modules hoisted.
2017-09-22 05:41:08 -04:00
"start": "webpack-dev-server",
"tap": "tap ./test/{unit,integration}/*.js",
"tap:unit": "tap ./test/unit/*.js",
"tap:integration": "tap ./test/integration/*.js",
ci: add initial CircleCI config This doesn't yet handle hotfixes or cron jobs
2022-06-02 14:00:14 -04:00
"test": "npm run lint && npm run tap",
Use unqualified paths in package.json scripts This allows stuff like yarn workspaces to function with node_modules hoisted.
2017-09-22 05:41:08 -04:00
"watch": "webpack --progress --colors --watch",
"version": "json -f package.json -I -e \"this.repository.sha = '$(git log -n1 --pretty=format:%H)'\""
Initial commit
2016-04-08 13:10:37 -04:00
},
chore: add Commitizen settings
2022-06-02 13:21:18 -04:00
"config": {
"commitizen": {
"path": "cz-conventional-changelog"
}
},
test: upgrade tap, configure coverage thresholds As part of simplifying the CI setup I plan to not explicitly specify `--jobs=4` to `tap` going forward. Upgrading to a newer version of `tap` means that it will automatically parallelize jobs according to available CPU count, which should be better anyway. Only one of our tests was incompatible with newer versions of `tap`, so this commit includes a compatibility fix there. Also, by default newer versions of `tap` calculate coverage and consider the test run to fail if below the configured thresholds. The default is 100% coverage and we're not there, so I adjusted the thresholds to match where we're at for now. We can ratchet those up over time.
2022-06-02 16:01:00 -04:00
"tap": {
chore(release): 1.1.7 [skip ci] ## [1.1.7](https://github.com/LLK/scratch-vm/compare/v1.1.6...v1.1.7) (2022-08-31) ### Bug Fixes * **deps:** update dependency scratch-semantic-release-config to v1.0.4 ([e57d1d5](https://github.com/LLK/scratch-vm/commit/e57d1d5da5185458ab97913bfe840540473ff850))
2022-08-31 17:57:30 -04:00
"branches": 60,
"functions": 70,
"lines": 70,
"statements": 70
test: upgrade tap, configure coverage thresholds As part of simplifying the CI setup I plan to not explicitly specify `--jobs=4` to `tap` going forward. Upgrading to a newer version of `tap` means that it will automatically parallelize jobs according to available CPU count, which should be better anyway. Only one of our tests was incompatible with newer versions of `tap`, so this commit includes a compatibility fix there. Also, by default newer versions of `tap` calculate coverage and consider the test run to fail if below the configured thresholds. The default is 100% coverage and we're not there, so I adjusted the thresholds to match where we're at for now. We can ratchet those up over time.
2022-06-02 16:01:00 -04:00
},
Use src/index as browser entry point Use src/index.js as the entry by default in tools building scratch-vm into a larger package. This saves file space by excluding extra webpack boilerplate and may allow for deeper optimizations. Depend on script dependencies for downstream webpack. For another package to build in scratch-vm's dependencies without them already being built into a consumed webpack build they need to be listed as dependencies. This can benefit large projects that reuse the same dependencies multiple times. Node will still use the main entry point and its webpack build leaves the dependencies as external references so it may reuse common modules in Node as well as in a build a browser environment.
2018-04-30 11:53:01 -04:00
"dependencies": {
fix(package): update @vernier/godirect to version 1.5.0 Closes #1961
2019-03-15 02:12:34 -04:00
"@vernier/godirect": "1.5.0",
Update npm packages to get new renderer and update benchmark for Bob Ross 🌲 (#1443)
2018-08-13 10:47:41 -04:00
"arraybuffer-loader": "^1.0.6",
Update atob, format-message, adm-zip, docdash, format-message-cli, tap, and webpack-cli modules
2018-08-30 11:23:34 -04:00
"atob": "2.1.2",
MicroBit extension, Scratch Link first draft. (#1230) * First microbit gui tests * Fixed JSONRPC inheritance. Renamed ScratchBLE/ScratchBT files. Removed ScratchBT test code from Microbit extension. Renamed addLine to log. * Fixed log comments. Removed addLine from Microbit. * Adding auto-connect to Microbit at extension loading. Adding hack for displayText block to Scratch-Link. * Resolved merge conflicts and brought in latest microbit extension example code. * Updated microbit write tests for displayText and displaySymbol blocks. Some linting. * Some linting and adding of BLE Characteristic consts. * Linting fixes. * Moving micro:bit device connection code all to the MicroBit class, decoupling Scratch3MicroBitBlocks from connection code. * Removing old disconenct handlers from MicroBit class. Moved service into new BLEUUID data structure. * Renamed _write to _send. Moved all BLE encoding concerns to the _send method. * Using the util log. Some linting. * Added _read method to MicroBit class. Renamed _send to _write. * Some linting and formatting comments. * First pass at peripheral chooser pattern for ScratchBLE. * Testing characteristicDidChange events, and some changes to ScratchBLE on ready events. * Refactoring work on PeripheralChooser and ScratchBLE. * Some variable renaming and method signature stubs. * Peripheral chooser method signatures. * Moved base64 encoding/decoding to util. Some method signature formatting. * Adding test stubs for new util and io classes. * Adding test stub for MicroBit extension. * Clean up for PR. * Clean up for PR. * Final cleanup for PR. * Removed logging to console. * Adding 'btoa' and 'atob' node modules and using them in Base64Util.
2018-06-18 14:56:51 -04:00
"btoa": "1.2.1",
Make canvas-toBlob a dependency
2018-05-31 17:29:38 -04:00
"canvas-toBlob": "1.0.0",
Use src/index as browser entry point Use src/index.js as the entry by default in tools building scratch-vm into a larger package. This saves file space by excluding extra webpack boilerplate and may allow for deeper optimizations. Depend on script dependencies for downstream webpack. For another package to build in scratch-vm's dependencies without them already being built into a consumed webpack build they need to be listed as dependencies. This can benefit large projects that reuse the same dependencies multiple times. Node will still use the main entry point and its webpack build leaves the dependencies as external references so it may reuse common modules in Node as well as in a build a browser environment.
2018-04-30 11:53:01 -04:00
"decode-html": "2.0.0",
fix(package): update diff-match-patch to version 1.0.4 Closes #1552
2018-09-04 06:19:05 -04:00
"diff-match-patch": "1.0.4",
fix(package): update format-message to version 6.2.1
2018-09-19 00:28:57 -04:00
"format-message": "6.2.1",
fix(package): update htmlparser2 to version 3.10.0
2018-10-21 17:11:10 -04:00
"htmlparser2": "3.10.0",
Use src/index as browser entry point Use src/index.js as the entry by default in tools building scratch-vm into a larger package. This saves file space by excluding extra webpack boilerplate and may allow for deeper optimizations. Depend on script dependencies for downstream webpack. For another package to build in scratch-vm's dependencies without them already being built into a consumed webpack build they need to be listed as dependencies. This can benefit large projects that reuse the same dependencies multiple times. Node will still use the main entry point and its webpack build leaves the dependencies as external references so it may reuse common modules in Node as well as in a build a browser environment.
2018-04-30 11:53:01 -04:00
"immutable": "3.8.1",
"jszip": "^3.1.5",
"minilog": "3.1.0",
feat(deps): update dependency scratch-parser to v5.1.1
2022-12-13 15:52:59 -05:00
"scratch-parser": "5.1.1",
fix(package): update scratch-sb1-converter to version 0.2.7
2019-02-15 10:11:54 -05:00
"scratch-sb1-converter": "0.2.7",
update translate-extension-languages module
2019-11-18 16:07:51 -05:00
"scratch-translate-extension-languages": "0.0.20191118205314",
update text-encoding to latest version
2019-03-04 13:01:37 -05:00
"text-encoding": "0.7.0",
Use src/index as browser entry point Use src/index.js as the entry by default in tools building scratch-vm into a larger package. This saves file space by excluding extra webpack boilerplate and may allow for deeper optimizations. Depend on script dependencies for downstream webpack. For another package to build in scratch-vm's dependencies without them already being built into a consumed webpack build they need to be listed as dependencies. This can benefit large projects that reuse the same dependencies multiple times. Node will still use the main entry point and its webpack build leaves the dependencies as external references so it may reuse common modules in Node as well as in a build a browser environment.
2018-04-30 11:53:01 -04:00
"worker-loader": "^1.1.1"
},
Move svg renderer to peer deps
2021-03-16 03:28:28 -04:00
"peerDependencies": {
"scratch-svg-renderer": "^0.2.0-prerelease"
},
Provide playground dependencies with webpack This confines all the files the playground needs to the playground directory.
2016-09-24 18:11:01 -04:00
"devDependencies": {
chore(deps): pin dependencies
2021-07-26 23:09:40 -04:00
"@babel/core": "7.13.10",
"@babel/preset-env": "7.14.8",
chore: add commitlint
2022-06-02 13:08:43 -04:00
"@commitlint/cli": "17.0.2",
"@commitlint/config-conventional": "17.0.2",
Update atob, format-message, adm-zip, docdash, format-message-cli, tap, and webpack-cli modules
2018-08-30 11:23:34 -04:00
"adm-zip": "0.4.11",
chore(deps): pin dependencies
2021-07-26 23:09:40 -04:00
"babel-eslint": "10.1.0",
"babel-loader": "8.2.2",
chore(deps): pin dependencies
2021-07-26 22:39:41 -04:00
"callsite": "1.0.0",
"copy-webpack-plugin": "4.5.4",
"docdash": "1.2.0",
"eslint": "5.3.0",
chore(deps): update dependency eslint-config-scratch to v5.1.0
2021-07-26 23:21:28 -04:00
"eslint-config-scratch": "5.1.0",
Update expose-loader dependency instead It doesn't make sense that webpack 4 has made Node 6 builds. Maybe it's due to peer dependencies on the install step?
2018-05-08 19:27:26 -04:00
"expose-loader": "0.7.5",
chore(deps): pin dependencies
2021-07-26 22:39:41 -04:00
"file-loader": "2.0.0",
chore(package): update format-message-cli to version 6.2.0
2018-09-12 11:10:04 -04:00
"format-message-cli": "6.2.0",
chore(deps): pin dependencies
2021-07-26 22:39:41 -04:00
"gh-pages": "1.2.0",
chore: add husky hook for commitlint
2022-06-02 13:14:41 -04:00
"husky": "8.0.1",
chore(deps): pin dependencies
2021-07-26 22:39:41 -04:00
"in-publish": "2.0.1",
Add tests for load costume error handling. Fix issue where asset data was not getting saved out properly.
2022-05-13 18:34:34 -04:00
"js-md5": "0.7.3",
chore(deps): upgrade lockfileVersion Also fix devDependencies order (`jsdoc` was out of place)
2022-06-02 12:36:53 -04:00
"jsdoc": "3.6.6",
Use caret ranges for dev dependencies These packages don't affect the output of the built package, so don't require a specific version. This should quiet Greenkeeper down a bit about our dependencies.
2017-02-20 17:13:40 -05:00
"json": "^9.0.4",
chore(package): update lodash.defaultsdeep to version 4.6.1
2019-07-09 20:44:57 -04:00
"lodash.defaultsdeep": "4.6.1",
chore(deps): pin dependencies
2021-07-26 22:39:41 -04:00
"pngjs": "3.3.3",
fix(deps): update dependency scratch-audio to v0.1.0-prerelease.20221123180128
2023-01-03 12:28:23 -05:00
"scratch-audio": "0.1.0-prerelease.20221123180128",
fix(deps): update dependency scratch-blocks to v0.1.0-prerelease.20230123071304
2023-01-23 02:58:32 -05:00
"scratch-blocks": "0.1.0-prerelease.20230123071304",
fix(deps): update dependency scratch-l10n to v3.15.20230123032119
2023-01-23 00:06:58 -05:00
"scratch-l10n": "3.15.20230123032119",
fix(deps): update dependency scratch-render to v0.1.0-prerelease.20221121051603
2023-01-03 23:13:48 -05:00
"scratch-render": "0.1.0-prerelease.20221121051603",
fix(deps): update dependency scratch-render-fonts to v1.0.0-prerelease.20221102164332
2023-01-04 02:10:51 -05:00
"scratch-render-fonts": "1.0.0-prerelease.20221102164332",
fix(deps): update dependency scratch-semantic-release-config to v1.0.5
2022-10-04 07:19:38 -04:00
"scratch-semantic-release-config": "1.0.5",
chore(deps): update dependency scratch-storage to v2.0.2
2022-05-26 07:58:44 -04:00
"scratch-storage": "2.0.2",
chore(deps): update dependency scratch-svg-renderer to v0.2.0-prerelease.20210727023023
2021-07-27 06:32:31 -04:00
"scratch-svg-renderer": "0.2.0-prerelease.20210727023023",
chore(package): update script-loader to version 0.7.2 Closes #678
2017-09-29 15:14:25 -04:00
"script-loader": "0.7.2",
ci: use a specific version of semantic-release
2023-01-09 13:12:55 -05:00
"semantic-release": "19.0.5",
chore(deps): pin dependencies
2021-07-26 22:39:41 -04:00
"stats.js": "0.17.0",
test: upgrade tap, configure coverage thresholds As part of simplifying the CI setup I plan to not explicitly specify `--jobs=4` to `tap` going forward. Upgrading to a newer version of `tap` means that it will automatically parallelize jobs according to available CPU count, which should be better anyway. Only one of our tests was incompatible with newer versions of `tap`, so this commit includes a compatibility fix there. Also, by default newer versions of `tap` calculate coverage and consider the test run to fail if below the configured thresholds. The default is 100% coverage and we're not there, so I adjusted the thresholds to match where we're at for now. We can ratchet those up over time.
2022-06-02 16:01:00 -04:00
"tap": "16.2.0",
chore(deps): pin dependencies
2021-07-26 22:39:41 -04:00
"tiny-worker": "2.3.0",
depend on uglifyjs-webpack-plugin uglifyjs-webpack-plugin is used in webpack.config.js.
2019-02-15 18:02:11 -05:00
"uglifyjs-webpack-plugin": "1.2.7",
chore(deps): pin dependencies
2021-07-26 22:39:41 -04:00
"webpack": "4.46.0",
"webpack-cli": "3.1.0",
"webpack-dev-server": "3.11.2"
Initial commit
2016-03-28 12:53:44 -04:00
}
}
Reference in a new issue Copy permalink