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

77 lines
2.2 KiB
JSON
Raw Normal View History

Issue #2654 - Lint with Travis-CI
2013-02-02 01:36:58 +09:00
{
"name": "pdf.js",
Version 2.0
2017-10-28 02:51:15 +09:00
"version": "2.0.0",
Redo and add more documentation to gh-pages.
2014-04-11 02:01:51 +09:00
"devDependencies": {
Update npm packages
2021-06-13 16:59:44 +09:00
"@babel/core": "^7.14.5",
"@babel/plugin-proposal-logical-assignment-operators": "^7.14.5",
"@babel/plugin-transform-modules-commonjs": "^7.14.5",
"@babel/plugin-transform-runtime": "^7.14.5",
"@babel/preset-env": "^7.14.5",
"@babel/runtime": "^7.14.5",
"acorn": "^8.4.0",
Update npm packages
2021-05-30 14:43:13 +09:00
"autoprefixer": "^10.2.6",
Update `npm` packages
2020-11-29 17:43:20 +09:00
"babel-loader": "^8.2.2",
Update npm packages
2021-05-30 14:43:13 +09:00
"canvas": "^2.8.0",
Update npm packages
2021-06-13 16:59:44 +09:00
"core-js": "^3.14.0",
Update `npm` packages
2020-12-13 19:38:37 +09:00
"cross-env": "^7.0.3",
Add a `DOMMatrix` polyfill for Node.js environments (PR 13361 follow-up) Given that `DOMMatrix` is, unsurprisingly, not supported in Node.js the `createMatrix` helper function in `src/display/pattern_helper.js` is most likely broken in Node.js environments. It will obviously try to fallback to the `DOMSVGFactory`, however that isn't intended for Node.js usage and errors will be thrown. Rather than trying to implement a `NodeSVGFactory`, this patch takes the easier route of just adding a `DOMMatrix` polyfill using: https://www.npmjs.com/package/dommatrix This isn't done only for simplicity, but it'll become necessary anyway since the `createMatrix` helper function is only temporary and will be removed in the future.
2021-06-10 17:50:35 +09:00
"dommatrix": "^0.0.6",
Update npm packages
2021-06-13 16:59:44 +09:00
"es-module-shims": "^0.10.7",
Update `escodegen` to version 2.0 This release contains support for additional modern ECMAScript features, such as e.g. the nullish coalescing operator `??` and the optional chaining operator `?.`.
2020-09-29 22:35:58 +09:00
"escodegen": "^2.0.0",
Update npm packages
2021-06-13 16:59:44 +09:00
"eslint": "^7.28.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-03-21 19:00:02 +09:00
"eslint-plugin-html": "^6.1.2",
Update npm packages
2021-05-30 14:43:13 +09:00
"eslint-plugin-import": "^2.23.4",
Add basic linting of JSON files using `eslint-plugin-json` By adding basic linting of JSON files, we can ensure that they're actually valid and prevent e.g. test-failures caused by *accidental* errors when editing the `test/test_manifest.json` file (something that I've done *many* times myself). For now this simply uses the `recommended` configuration, but we can obviously tweak this later if/when needed. Please find additional information at https://github.com/azeemba/eslint-plugin-json
2021-06-15 18:59:47 +09:00
"eslint-plugin-json": "^3.0.0",
Update `npm` packages
2021-04-18 18:02:42 +09:00
"eslint-plugin-mozilla": "^2.10.0",
"eslint-plugin-no-unsanitized": "^3.1.5",
"eslint-plugin-prettier": "^3.4.0",
Update Puppeteer to version 9 (#13282) * Update Puppeteer to version 9 Hopefully the updated Chromium-version might help reduce the number of intermittent test failures. Please find additional information at https://github.com/puppeteer/puppeteer/releases/tag/v9.0.0 * Update the `eslint-plugin-sort-exports`/`eslint-plugin-unicorn"` packages to their latest versions Both of these ESLint plugins have increased their version numbers, however `npm update` doesn't handle this automatically. https://www.npmjs.com/package/eslint-plugin-sort-exports https://www.npmjs.com/package/eslint-plugin-unicorn
2021-04-22 18:35:16 +09:00
"eslint-plugin-sort-exports": "^0.4.0",
Update the `eslint-plugin-unicorn` package to the latest version
2021-06-13 17:03:08 +09:00
"eslint-plugin-unicorn": "^33.0.1",
Update npm packages
2021-05-30 14:43:13 +09:00
"globals": "^13.9.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"gulp": "^4.0.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
"gulp-postcss": "^9.0.0",
"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",
"jasmine": "^3.7.0",
Update npm packages
2021-05-16 17:05:58 +09:00
"jsdoc": "^3.6.7",
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
2021-01-10 19:25:47 +09:00
"needle": "^2.6.0",
Update npm packages
2021-06-13 16:59:44 +09:00
"postcss": "^8.3.2",
Update the `postcss-calc` package to the latest version I've successfully run `gulp mozcentral` and `gulp generic` locally, with/without this patch and diff-ed the *built* `web/viewer.css` files. There were no changes, in the build-output, caused by this update. https://www.npmjs.com/package/postcss-calc
2021-04-14 22:31:58 +09:00
"postcss-calc": "^8.0.0",
Update npm packages
2021-06-13 16:59:44 +09:00
"prettier": "^2.3.1",
Update Puppeteer to version 10 Hopefully the updated Chromium-version might help reduce the number of intermittent test failures. Please find additional information at https://github.com/puppeteer/puppeteer/releases/tag/v10.0.0
2021-06-01 21:55:19 +09:00
"puppeteer": "^10.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-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-05-02 16:30:09 +09:00
"stylelint": "^13.13.1",
Add (basic) support for Stylelint, to allow linting of CSS files This is *similar* to the existing linting for JavaScript files, but covers CSS files instead. While there's a lot of rules that could potentially be used, the main advantage of using Stylelint is that it has Prettier integration which means that we can automatically enforce a *consistent* style for our CSS files as well. As a proof of concept, this patch is purposely limited to: - Adding a simple rule, here `block-no-empty` is chosen; see https://stylelint.io/user-guide/rules/block-no-empty - Adding Prettier integration, to unify the style of our CSS files. Please find additional information at https://stylelint.io/
2020-08-29 23:35:27 +09:00
"stylelint-config-prettier": "^8.0.2",
Update `npm` packages
2021-03-07 20:00:57 +09:00
"stylelint-prettier": "^1.2.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-05-02 16:30:09 +09:00
"terser": "^5.7.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
2021-05-30 14:43:13 +09:00
"typescript": "^4.3.2",
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-04-18 18:02:42 +09:00
"web-streams-polyfill": "^3.0.3",
Update npm packages
2021-05-30 14:43:13 +09:00
"webpack": "^5.38.1",
Allow minor and patch versions for the `webpack-stream` dependency again Fixes #11996.
2021-02-21 23:13:41 +09:00
"webpack-stream": "^6.1.2",
Update packages
2018-11-25 05:00:22 +09:00
"wintersmith": "^2.5.0",
Update the `yargs` package to the latest version
2021-05-30 14:51:30 +09:00
"yargs": "^17.0.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": {
Upgrade Puppeteer to version 5.3.1
2020-10-04 06:06:31 +09:00
"postinstall": "cross-env PUPPETEER_PRODUCT=firefox node node_modules/puppeteer/install.js",
[api-minor] Produce non-translated/non-polyfilled builds by default
2019-10-15 04:19:31 +09:00
"test": "gulp npm-test"
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