Sakurai/pdf.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
48139a0059
pdf.js/package.json

74 lines
2.1 KiB
JSON
Raw Normal View History

Issue #2654 - Lint with Travis-CI
2013-02-02 01:36:58 +09:00
{
"name": "pdf.js",
Redo and add more documentation to gh-pages.
2014-04-11 02:01:51 +09:00
"devDependencies": {
Update npm packages
2022-01-23 18:58:15 +09:00
"@babel/core": "^7.16.12",
"@babel/plugin-transform-modules-commonjs": "^7.16.8",
"@babel/plugin-transform-runtime": "^7.16.10",
"@babel/preset-env": "^7.16.11",
Update npm packages
2022-01-09 18:05:52 +09:00
"@babel/runtime": "^7.16.7",
Update npm packages
2021-10-31 17:38:18 +09:00
"@javascript-obfuscator/escodegen": "2.2.2",
Update npm packages
2022-01-09 18:05:52 +09:00
"acorn": "^8.7.0",
"autoprefixer": "^10.4.2",
Update npm packages
2021-10-31 17:38:18 +09:00
"babel-loader": "^8.2.3",
Update npm packages
2022-01-23 18:58:15 +09:00
"canvas": "^2.9.0",
Polyfill `structuredClone` with core-js (PR 13948 follow-up) This allows us to remove the manually implemented `structuredClone` polyfill, thus reducing the maintenance burden for the `LoopbackPort` class; refer to https://github.com/zloirock/core-js#structuredclone *Please note:* While `structuredClone` support landed already in Firefox 94, Google Chrome only added it in version 98 (currently in Beta). However, given that the `LoopbackPort` will only be used together with *fake workers* in browsers this shouldn't be too much of a problem.[1] For Node.js environments, where *fake workers* are unfortunately necessary, using a `legacy/`-build is already required which thus guarantees that the `structuredClone` polyfill is available. Also, the patch updates core-js to the latest version since that one includes `structuredClone` improvements; please see https://github.com/zloirock/core-js/releases/tag/v3.20.3 --- [1] Given that we only support browsers with proper worker support, if *fake workers* are being used that essentially indicates a configuration problem/error.
2022-01-18 21:07:39 +09:00
"core-js": "^3.20.3",
Update `npm` packages
2020-12-13 19:38:37 +09:00
"cross-env": "^7.0.3",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"dommatrix": "^0.0.24",
Update npm packages
2021-12-26 19:09:29 +09:00
"es-module-shims": "^1.4.1",
Update npm packages
2022-01-23 18:58:15 +09:00
"eslint": "^8.7.0",
Update npm packages
2021-05-02 16:30:09 +09:00
"eslint-config-prettier": "^8.3.0",
Update the `eslint-plugin-mozilla` to the latest version (PR 10905 follow-up) This required adding a number of additional dependencies, based on https://dxr.mozilla.org/mozilla-central/rev/4aed8e10318f38571712350856bf9e61c5f84e1f/tools/lint/eslint/eslint-plugin-mozilla/package.json#32-37 Since this, implicitly, enabled "prettier"[1] for the `extensions/firefox` directory a couple of small code changes were necessary as well. --- [1] Generally speaking I'm wondering if that name is deliberately ironic, since the style it enforces is often times extremely weird and ugly :-P
2019-09-07 19:37:13 +09:00
"eslint-plugin-fetch-options": "^0.0.5",
Update npm packages
2021-10-03 15:21:01 +09:00
"eslint-plugin-html": "^6.2.0",
Update npm packages
2022-01-09 18:05:52 +09:00
"eslint-plugin-import": "^2.25.4",
Update npm packages
2021-08-08 17:45:36 +09:00
"eslint-plugin-json": "^3.1.0",
Update npm packages
2021-10-03 15:21:01 +09:00
"eslint-plugin-mozilla": "^2.11.1",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"eslint-plugin-no-unsanitized": "^4.0.1",
Update the `eslint-plugin-prettier` package to the latest version Please refer to https://github.com/prettier/eslint-plugin-prettier/blob/master/CHANGELOG.md#v400-2021-08-30
2021-09-05 16:54:18 +09:00
"eslint-plugin-prettier": "^4.0.0",
Update ESLint to version 8 Please refer to https://eslint.org/docs/8.0.0/user-guide/migrating-to-8.0.0 Given that this is a major version increase it also required updating ESLint plugins, see https://github.com/sindresorhus/eslint-plugin-unicorn/releases and https://github.com/jrdrg/eslint-plugin-sort-exports/releases
2021-10-17 18:42:09 +09:00
"eslint-plugin-sort-exports": "^0.6.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"eslint-plugin-unicorn": "^40.1.0",
Update npm packages
2021-10-31 17:38:18 +09:00
"globals": "^13.12.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"gulp": "^4.0.2",
Update npm packages
2021-09-05 16:47:57 +09:00
"gulp-postcss": "^9.0.1",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"gulp-rename": "^2.0.0",
Update npm packages
2021-05-16 17:05:58 +09:00
"gulp-replace": "^1.1.3",
Update `npm` packages
2021-03-21 19:00:02 +09:00
"gulp-zip": "^5.1.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"jasmine": "^4.0.2",
"jsdoc": "^3.6.9",
Include forgotten changes after Wintersmith update This should have been part of the previous commit that updated the Wintersmith dependency. Markdown support is no longer included in Pug itself and should be done by a transformer instead.
2018-11-25 05:39:54 +09:00
"jstransformer-markdown-it": "^2.1.0",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"merge-stream": "^2.0.0",
Update `npm` packages
2020-04-18 18:08:46 +09:00
"mkdirp": "^1.0.4",
Update the `needle` package to the latest version
2021-09-05 16:56:50 +09:00
"needle": "^3.0.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"postcss": "^8.4.5",
Update npm packages
2022-01-23 18:58:15 +09:00
"postcss-calc": "^8.2.2",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"prettier": "^2.5.1",
Update Puppeteer to version `13.1.2` Note in particular https://github.com/puppeteer/puppeteer/releases/tag/v13.1.0 which includes an update to Chromium 98, which adds support for `structuredClone` in the browser.
2022-01-18 20:23:22 +09:00
"puppeteer": "^13.1.2",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"rimraf": "^3.0.2",
Update all npm packages to the latest versions
2018-01-31 23:51:03 +09:00
"streamqueue": "^1.1.2",
Update npm packages
2021-12-26 19:09:29 +09:00
"stylelint": "^14.2.0",
Update the `stylelint-config-prettier` package to the latest version Please refer to https://github.com/prettier/stylelint-config-prettier/releases
2021-10-17 18:37:40 +09:00
"stylelint-config-prettier": "^9.0.3",
Update Stylelint to version 14 (along with related packages) Based on https://github.com/stylelint/stylelint/blob/14.0.0/docs/migration-guide/to-14.md none of the changes look directly relevant for us.
2021-11-28 20:36:16 +09:00
"stylelint-prettier": "^2.0.0",
Update packages
2019-01-21 00:34:24 +09:00
"systemjs": "^0.21.6",
Update all packages to the most recent version To support this, the following changes have to be made as well: - Ignore `package-lock.json` since NPM creates it, but we should not have it in the repository. - Switch from `babel-preset-es2015` to `babel-preset-env` to resolve the deprecation warning in the test logs. The latter is more recent and flexible, but should be the same functionality-wise. - `transform` now needs to have the `utf-8` encoding option provided. If not given, it will call the callback with a `Buffer` object, which results in an unhandled promise rejection since what is returned from the callback is a string, not a `Buffer`.
2017-09-30 06:34:54 +09:00
"systemjs-plugin-babel": "^0.0.25",
Update npm packages
2021-11-28 18:40:29 +09:00
"terser": "^5.10.0",
Upgrade minor/major versions of dependencies that don't require code changes The changelogs of those dependencies showed no breaking changes for us. Most of the time the major version bump was done to remove compatibility with very outdated Node.js versions. Only for `autoprefixer` and `gulp-postcss` a change was required, which is including `postcss` in our `package.json` explicitly since it's now a peer dependency of those packages. Now only `acorn`,`systemjs`, `terser` and `yargs` are not the latest versions because they require more work.
2020-10-05 01:53:43 +09:00
"through2": "^4.0.2",
"ttest": "^3.0.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"typescript": "^4.5.5",
Update packages
2018-07-01 03:39:31 +09:00
"typogr": "^0.6.8",
Update `npm` packages
2020-10-04 20:49:28 +09:00
"vinyl": "^2.2.1",
Update packages
2018-05-20 21:21:08 +09:00
"vinyl-fs": "^3.0.3",
Update npm packages
2021-11-14 18:17:30 +09:00
"web-streams-polyfill": "^3.2.0",
Update npm packages
2022-01-23 18:58:15 +09:00
"webpack": "^5.67.0",
Update the `webpack-stream` package to the latest version
2021-09-05 16:58:59 +09:00
"webpack-stream": "^7.0.0",
Update packages
2018-11-25 05:00:22 +09:00
"wintersmith": "^2.5.0",
Update npm packages
2021-12-26 19:09:29 +09:00
"yargs": "^17.3.1"
Redo and add more documentation to gh-pages.
2014-04-11 02:01:51 +09:00
},
Issue #2654 - Lint with Travis-CI
2013-02-02 01:36:58 +09:00
"scripts": {
Remove the `npm test`-command This command was added all the way back when basic CI-support was first introduced (using Travis at the time), however it's never really intended to be used e.g. for local development. By having a `npm test`-command listed in the `package.json` file, there's a very real risk that someone unfamiliar with the code-base would only run that one and thus miss all the other (more important) test-suites[1]. Hence this patch which removes the `npm test`-command, and instead simply calls the relevant gulp-task[2] directly in the GitHub Actions configuration. --- [1] Which consist of the unit-tests (run in browsers), the font-tests (potentially), the reference-tests, and the integration-tests. [2] Which is also renamed slightly, to better fit its current usage.
2021-08-27 23:07:07 +09:00
"postinstall": "cross-env PUPPETEER_PRODUCT=firefox node node_modules/puppeteer/install.js"
Issue #2654 - Lint with Travis-CI
2013-02-02 01:36:58 +09:00
},
"repository": {
"type": "git",
"url": "git://github.com/mozilla/pdf.js.git"
Add PDF.js license to package.json
2013-03-27 17:16:40 +09:00
},
Clean up npm dependencies and add `license` property underscore and moment were not used anywhere
2015-07-01 12:20:48 +09:00
"license": "Apache-2.0"
Issue #2654 - Lint with Travis-CI
2013-02-02 01:36:58 +09:00
}
Reference in New Issue Copy Permalink