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

73 lines
2.0 KiB
JSON
Raw Normal View History

Issue #2654 - Lint with Travis-CI
2013-02-01 11:36:58 -05:00
{
"name": "pdf.js",
Redo and add more documentation to gh-pages.
2014-04-10 10:01:51 -07:00
"devDependencies": {
Update npm packages
2023-05-28 09:39:34 +02:00
"@babel/core": "^7.22.1",
Update npm packages
2023-05-14 10:12:06 +02:00
"@babel/plugin-transform-modules-commonjs": "^7.21.5",
Update npm packages
2023-05-28 09:39:34 +02:00
"@babel/preset-env": "^7.22.2",
"@babel/runtime": "^7.22.3",
Update the `@javascript-obfuscator/escodegen` package to the latest version The only changes are support for [Class static initialization blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Class_static_initialization_blocks), and the diff for the `node_modules\@javascript-obfuscator\escodegen\escodegen.js` file contains only: ```diff @@ -1506,6 +1506,13 @@ return result; }, + StaticBlock: function (stmt, flags) { + return [ + 'static' + space, + this.BlockStatement(stmt, flags) + ]; + }, + ThrowStatement: function (stmt, flags) { return [join( 'throw', ```
2022-02-06 11:26:07 +01:00
"@javascript-obfuscator/escodegen": "2.3.0",
Update npm packages
2023-01-28 08:13:13 +01:00
"acorn": "^8.8.2",
Update npm packages
2023-03-12 10:27:52 +01:00
"autoprefixer": "^10.4.14",
Update npm packages
2023-01-15 10:34:56 +01:00
"babel-loader": "^9.1.2",
Update npm packages
2023-05-28 09:39:34 +02:00
"caniuse-lite": "^1.0.30001489",
Update npm packages
2023-04-15 22:08:58 +02:00
"canvas": "^2.11.2",
Update npm packages
2023-05-14 10:12:06 +02:00
"core-js": "^3.30.2",
Update `npm` packages
2020-12-13 11:38:37 +01:00
"cross-env": "^7.0.3",
Pin the `es-module-shims` dependency to version 1.4.7 Unfortunately newer versions either caused breakage when running the unit tests manually in a browser or when serving the development viewer. Given that we hope to use native import maps soon and this dependency will then be removed anyway, let's pin it for the time being.
2022-05-01 14:02:43 +02:00
"es-module-shims": "1.4.7",
Update npm packages
2023-05-28 09:39:34 +02:00
"eslint": "^8.41.0",
Update npm packages
2023-03-25 09:41:15 +01:00
"eslint-config-prettier": "^8.8.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 12:37:13 +02:00
"eslint-plugin-fetch-options": "^0.0.5",
Update npm packages
2022-08-07 10:20:21 +02:00
"eslint-plugin-html": "^7.1.0",
Update npm packages
2023-01-28 08:13:13 +01:00
"eslint-plugin-import": "^2.27.5",
Update npm packages
2021-08-08 10:45:36 +02:00
"eslint-plugin-json": "^3.1.0",
Update `eslint-plugin-mozilla` to avoid having to force-install packages (issue 15429) The latest version of `eslint-plugin-mozilla` removed the Prettier dependency, see https://bugzilla.mozilla.org/show_bug.cgi?id=1677562, which means that we no longer need to use `npm install --force` in the PDF.js library.
2023-04-20 16:09:13 +02:00
"eslint-plugin-mozilla": "^3.1.0",
Update npm packages
2022-11-27 10:18:30 +01:00
"eslint-plugin-no-unsanitized": "^4.0.2",
Update npm packages
2022-07-10 10:43:08 +02:00
"eslint-plugin-prettier": "^4.2.1",
Update npm packages
2022-11-13 21:28:21 +01:00
"eslint-plugin-sort-exports": "^0.8.0",
Update npm packages
2023-05-14 10:12:06 +02:00
"eslint-plugin-unicorn": "^47.0.0",
Update npm packages
2023-02-11 10:24:22 +01:00
"globals": "^13.20.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 16:36:42 +02:00
"gulp": "^4.0.2",
Update npm packages
2021-09-05 09:47:57 +02: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-04 18:53:43 +02:00
"gulp-rename": "^2.0.0",
Update npm packages
2022-12-25 12:26:23 +01:00
"gulp-replace": "^1.1.4",
Update `npm` packages
2021-03-21 11:00:02 +01:00
"gulp-zip": "^5.1.0",
Update `jasmine` to version 5 Despite this being a *major* version increase, it doesn't appear to require any updates in our test-suites. Note in particular that the minimum supported browsers/environments were updated, however this isn't a problem given our recent support-changes in the PDF.js library. Please find additional details at https://github.com/jasmine/jasmine/blob/main/release_notes/5.0.0.md
2023-05-14 12:57:31 +02:00
"jasmine": "^5.0.0",
Update npm packages
2023-03-12 10:27:52 +01:00
"jsdoc": "^4.0.2",
Update dependencies to the most recent versions
2022-10-01 18:02:00 +02:00
"jstransformer-markdown-it": "^3.0.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-04 18:53:43 +02:00
"merge-stream": "^2.0.0",
Update npm packages
2023-05-14 10:12:06 +02:00
"mkdirp": "^3.0.1",
Update npm packages
2022-11-27 10:18:30 +01:00
"needle": "^3.2.0",
Polyfill `Path2D` in Node.js environments Until just recently the only existing `Path2D` polyfill didn't have support for Node.js and/or the `node-canvas` package. Given that this was just fixed, in the latest version, we can now finally remove our inline-checks at the relevant call-sites; please also see https://github.com/nilzona/path2d-polyfill#usage-with-node-canvas
2023-01-22 17:01:06 +01:00
"path2d-polyfill": "^2.0.1",
Update packages to the most recent versions
2023-04-23 13:48:22 +02:00
"postcss": "^8.4.23",
Update npm packages
2023-02-11 10:24:22 +01:00
"postcss-dir-pseudo-class": "^7.0.2",
Update packages to the most recent versions
2023-04-23 13:48:22 +02:00
"prettier": "^2.8.8",
Update npm packages
2022-10-16 09:09:38 +02:00
"puppeteer": "^19.0.0",
Revert "Update `rimraf` to version 4" This reverts commit 32357e3d172a552e0408b3e1ed743e87fe7d5a21.
2023-03-06 19:47:18 +01:00
"rimraf": "^3.0.2",
Update all npm packages to the latest versions
2018-01-31 15:51:03 +01:00
"streamqueue": "^1.1.2",
Update npm packages
2023-05-28 09:39:34 +02:00
"stylelint": "^15.6.2",
Update npm packages
2023-03-12 10:27:52 +01:00
"stylelint-prettier": "^3.0.0",
Update npm packages
2023-05-28 09:39:34 +02:00
"terser": "^5.17.6",
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-04 18:53:43 +02:00
"through2": "^4.0.2",
Update dependencies to the most recent versions
2022-04-02 16:19:17 +02:00
"ttest": "^4.0.0",
Update TypeScript to version `5` Note that this is a major version increase, however the `gulp types` and `gulp typestest` tasks seem to work as-is; please see https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/
2023-04-16 11:29:38 +02:00
"typescript": "^5.0.4",
Update packages
2018-06-30 20:39:31 +02:00
"typogr": "^0.6.8",
Update dependencies to the most recent versions
2022-10-01 18:02:00 +02:00
"vinyl": "^3.0.0",
Update packages
2018-05-20 14:21:08 +02:00
"vinyl-fs": "^3.0.3",
Update npm packages
2023-05-28 09:39:34 +02:00
"webpack": "^5.84.1",
Update the `webpack-stream` package to the latest version
2021-09-05 09:58:59 +02:00
"webpack-stream": "^7.0.0",
Update packages
2018-11-24 21:00:22 +01:00
"wintersmith": "^2.5.0",
Update npm packages
2023-05-14 10:12:06 +02:00
"yargs": "^17.7.2"
Redo and add more documentation to gh-pages.
2014-04-10 10:01:51 -07:00
},
Issue #2654 - Lint with Travis-CI
2013-02-01 11:36:58 -05: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 16:07:07 +02:00
"postinstall": "cross-env PUPPETEER_PRODUCT=firefox node node_modules/puppeteer/install.js"
Issue #2654 - Lint with Travis-CI
2013-02-01 11:36:58 -05:00
},
"repository": {
"type": "git",
"url": "git://github.com/mozilla/pdf.js.git"
Add PDF.js license to package.json
2013-03-27 01:16:40 -07:00
},
[api-minor] Update the minimum supported Node.js version to 16 This patch updates the minimum supported environments as follows: - Node.js 16, which was released on 2021-04-20; see https://en.wikipedia.org/wiki/Node.js#Releases Note also that Node.js 14 will very soon reach EOL, and thus no longer receive any security updates.
2023-03-07 12:03:45 +01:00
"engines": {
[api-minor] Update the minimum supported Node.js version to 18 This patch updates the minimum supported environments as follows: - Node.js 18, which was released on 2022-04-19; see https://en.wikipedia.org/wiki/Node.js#Releases Note also that Node.js 16 will soon reach EOL, and thus no longer receive any security updates.
2023-04-05 10:40:19 +02:00
"node": ">=18"
[api-minor] Update the minimum supported Node.js version to 16 This patch updates the minimum supported environments as follows: - Node.js 16, which was released on 2021-04-20; see https://en.wikipedia.org/wiki/Node.js#Releases Note also that Node.js 14 will very soon reach EOL, and thus no longer receive any security updates.
2023-03-07 12:03:45 +01:00
},
Clean up npm dependencies and add `license` property underscore and moment were not used anywhere
2015-06-30 20:20:48 -07:00
"license": "Apache-2.0"
Issue #2654 - Lint with Travis-CI
2013-02-01 11:36:58 -05:00
}
Reference in New Issue Copy Permalink