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

78 lines
2.3 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-07-10 17:43:08 +09:00
"@babel/core": "^7.18.6",
"@babel/plugin-transform-modules-commonjs": "^7.18.6",
"@babel/plugin-transform-runtime": "^7.18.6",
"@babel/preset-env": "^7.18.6",
"@babel/runtime": "^7.18.6",
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 19:26:07 +09:00
"@javascript-obfuscator/escodegen": "2.3.0",
Update dependencies to the most recent versions There are two notable changes here: - `dommatrix` is a major version upgrade, but looking through the commit history of their `package.json` file at https://github.com/thednp/dommatrix/commits/master/package.json (due to the lack of a changelog) I couldn't find any breaking changes. - `es-module-shims` is a regular update, but it was previously pinned for causing intermittent breakage when running the unit tests in a browser manually. Fortunately this cannot be reproduced anymore with the most recent version, so we can also put the caret back now.
2022-05-01 02:56:10 +09:00
"acorn": "^8.7.1",
Update npm packages
2022-05-15 16:02:57 +09:00
"autoprefixer": "^10.4.7",
Update dependencies to the most recent versions There are two notable changes here: - `dommatrix` is a major version upgrade, but looking through the commit history of their `package.json` file at https://github.com/thednp/dommatrix/commits/master/package.json (due to the lack of a changelog) I couldn't find any breaking changes. - `es-module-shims` is a regular update, but it was previously pinned for causing intermittent breakage when running the unit tests in a browser manually. Fortunately this cannot be reproduced anymore with the most recent version, so we can also put the caret back now.
2022-05-01 02:56:10 +09:00
"babel-loader": "^8.2.5",
Update npm packages
2022-07-10 17:43:08 +09:00
"caniuse-lite": "^1.0.30001364",
Update dependencies to the most recent versions Note that even though Puppeteer got a major version bump the changelog doesn't include compatibility changes that are relevant to us; please see https://github.com/puppeteer/puppeteer/releases.
2022-06-25 23:27:24 +09:00
"canvas": "^2.9.3",
Update npm packages
2022-07-10 17:43:08 +09:00
"core-js": "^3.23.4",
Update `npm` packages
2020-12-13 19:38:37 +09:00
"cross-env": "^7.0.3",
Add a `<dialog>` polyfill for the `generic-legacy` build Please note that this patch is purposely quite basic, e.g. it doesn't add the polyfill-CSS in order to simplify the build process, and things such as `::backdrop` thus isn't working. However, this patch does ensure that older browsers can at least still *access* all of the previous overlays and that things like e.g. opening of password-protected documents respectively printing still works.
2022-03-25 22:10:33 +09:00
"dialog-polyfill": "^0.5.6",
Update npm packages
2022-05-15 16:02:57 +09:00
"dommatrix": "^1.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 21:02:43 +09:00
"es-module-shims": "1.4.7",
Update npm packages
2022-07-10 17:43:08 +09:00
"eslint": "^8.19.0",
Update npm packages
2022-03-06 18:28:00 +09:00
"eslint-config-prettier": "^8.5.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-04-17 17:15:10 +09:00
"eslint-plugin-import": "^2.26.0",
Update npm packages
2021-08-08 17:45:36 +09:00
"eslint-plugin-json": "^3.1.0",
Update npm packages
2022-07-10 17:43:08 +09:00
"eslint-plugin-mozilla": "^2.12.4",
Update packages to the most recent versions
2021-12-11 23:24:26 +09:00
"eslint-plugin-no-unsanitized": "^4.0.1",
Update npm packages
2022-07-10 17:43:08 +09:00
"eslint-plugin-prettier": "^4.2.1",
"eslint-plugin-sort-exports": "^0.7.0",
"eslint-plugin-unicorn": "^43.0.1",
[editor] Use the `fit-curve` package (issue 15004) Rather than including all of this external code in the PDF.js repository, we should be using the npm package instead. Unfortunately this is slightly more complicated than you'd hope, since the `fit-curve` package (which is older) isn't directly compatible with modern JavaScript modules. In particular, the following cases needed to be considered: - For the development viewer (i.e. `gulp server`) and the unit-tests, we thus need to build a fitCurve-bundle that can be directly `import`ed. - For the actual PDF.js build-targets, we can slightly reduce the sizes by depending on the "raw" `fit-curve` source-code. - For the Node.js unit-tests, the `fit-curve` package can be used as-is.
2022-07-07 06:02:53 +09:00
"fit-curve": "^0.2.0",
Update npm packages
2022-07-10 17:43:08 +09:00
"globals": "^13.16.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 dependencies to the most recent versions Note that even though Puppeteer got a major version bump the changelog doesn't include compatibility changes that are relevant to us; please see https://github.com/puppeteer/puppeteer/releases.
2022-06-25 23:27:24 +09:00
"jasmine": "^4.2.1",
Update npm packages
2022-02-06 19:24:14 +09:00
"jsdoc": "^3.6.10",
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 npm packages
2022-04-17 17:15:10 +09:00
"needle": "^3.1.0",
Update npm packages
2022-05-29 16:28:39 +09:00
"postcss": "^8.4.14",
Update npm packages
2022-07-10 17:43:08 +09:00
"postcss-dir-pseudo-class": "^6.0.5",
Replace `dir`-dependent `margin`/`margin-left`/`margin-right` with logical properties *Please note:* This is another step in what will, time permitting, become a series of patches to simplify/modernize the viewer CSS. Rather than having to manually specify ltr/rtl-specific margin-values in the CSS, we can use logical margin instead (and similar for some related left/right occurrences). These logical properties depend on, among other things, the direction of the HTML document which we *always* specify in the viewer. Given that most of these logical CSS properties are fairly new, and that cross-browser support is thus somewhat limited (see below), we need to use a couple of PostCSS plugins (see below) in order to support this in the GENERIC viewer. - https://developer.mozilla.org/en-US/docs/Web/CSS/margin-inline#browser_compatibility - https://developer.mozilla.org/en-US/docs/Web/CSS/margin-inline-start#browser_compatibility - https://developer.mozilla.org/en-US/docs/Web/CSS/margin-inline-end#browser_compatibility - https://developer.mozilla.org/en-US/docs/Web/CSS/inset-inline-start#browser_compatibility - https://developer.mozilla.org/en-US/docs/Web/CSS/inset-inline-end#browser_compatibility --- - https://github.com/csstools/postcss-plugins/tree/main/plugins/postcss-logical - https://github.com/csstools/postcss-plugins/tree/main/plugins/postcss-dir-pseudo-class
2022-03-14 02:30:51 +09:00
"postcss-logical": "^5.0.4",
Update dependencies to the most recent versions Note that even though Puppeteer got a major version bump the changelog doesn't include compatibility changes that are relevant to us; please see https://github.com/puppeteer/puppeteer/releases.
2022-06-25 23:27:24 +09:00
"prettier": "^2.7.1",
Update npm packages
2022-07-10 17:43:08 +09:00
"puppeteer": "^15.3.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
2022-06-12 21:02:31 +09:00
"stylelint": "^14.9.1",
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",
Bump terser from 5.14.1 to 5.14.2 Bumps [terser](https://github.com/terser/terser) from 5.14.1 to 5.14.2. - [Release notes](https://github.com/terser/terser/releases) - [Changelog](https://github.com/terser/terser/blob/master/CHANGELOG.md) - [Commits](https://github.com/terser/terser/commits) --- updated-dependencies: - dependency-name: terser dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
2022-07-21 15:01:41 +09:00
"terser": "^5.14.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
"through2": "^4.0.2",
Update dependencies to the most recent versions
2022-04-02 23:19:17 +09:00
"ttest": "^4.0.0",
Update dependencies to the most recent versions Note that even though Puppeteer got a major version bump the changelog doesn't include compatibility changes that are relevant to us; please see https://github.com/puppeteer/puppeteer/releases.
2022-06-25 23:27:24 +09:00
"typescript": "^4.7.4",
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
2022-04-17 17:15:10 +09:00
"web-streams-polyfill": "^3.2.1",
Update npm packages
2022-06-12 21:02:31 +09:00
"webpack": "^5.73.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
2022-05-29 16:28:39 +09:00
"yargs": "^17.5.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