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

75 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
2020-09-06 18:49:49 +09:00
"@babel/core": "^7.11.6",
Update `npm` packages
2020-07-13 18:05:50 +09:00
"@babel/plugin-proposal-nullish-coalescing-operator": "^7.10.4",
Add basic support for the optional chaining operator `?.` For now we need to use a Babel-plugin, since part of our build system doesn't support this fully (e.g. Babel-loader, Webpack 4.x, and SystemJS). While the `?.` operator will thus always be transpiled by Babel, even in modern builds, simply supporting it for development purposes seems like a step in the right direction. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining
2020-09-29 22:45:05 +09:00
"@babel/plugin-proposal-optional-chaining": "^7.11.0",
Update `npm` packages
2020-07-13 18:05:50 +09:00
"@babel/plugin-transform-modules-commonjs": "^7.10.4",
Update `npm` packages
2020-09-06 18:49:49 +09:00
"@babel/plugin-transform-runtime": "^7.11.5",
"@babel/preset-env": "^7.11.5",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"@babel/runtime": "^7.11.2",
"acorn": "^7.4.0",
"autoprefixer": "^9.8.6",
Update `npm` packages
2020-04-02 19:13:14 +09:00
"babel-loader": "^8.1.0",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"canvas": "^2.6.1",
Update `npm` packages
2020-04-18 18:08:46 +09:00
"core-js": "^3.6.5",
Introduce Puppeteer for handling browsers during tests This commit replaces our own infrastructure for handling browsers during tests with Puppeteer. Using our own infrastructure for this had a few downsides: - It has proven to not always be reliable, especially when closing the browser, causing failures on the bots because browsers were still running even though they should have been stopped. Puppeteer should do a better job with this because it uses the browser's test built-in instrumentation tools for this (the devtools protocol) which our code didn't. This also means that we don't have to pass parameters/preferences to tweak browser behavior anymore. - It requires the browsers under test to be installed on the system, whereas Puppeteer downloads the browsers before the test. This means that setup is much easier (no more manual installations and browser manifest files) as well as testing with different browser versions (since they can be provisioned on demand). Moreover, this ensures that contributors always run the tests in both Firefox and Chrome, regardless of which browsers they have installed locally. - It's all code we have to maintain, so Puppeteer abstracts away how the browsers start/stop for us so we don't have to keep that code. By default, Puppeteer only installs one browser during installation, hence the need for a post-install script to install the second browser. This requires `cross-env` to make passing the environment variable work on both Linux and Windows.
2020-04-19 00:46:58 +09:00
"cross-env": "^7.0.2",
Update `npm` packages
2020-06-27 18:30:30 +09:00
"es-module-shims": "^0.4.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
2020-10-04 20:49:28 +09:00
"eslint": "^7.10.0",
"eslint-config-prettier": "^6.12.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
2020-09-20 18:34:24 +09:00
"eslint-plugin-html": "^6.1.0",
Update `npm` packages
2020-10-04 20:49:28 +09:00
"eslint-plugin-import": "^2.22.1",
Update `npm` packages
2020-08-09 18:03:07 +09:00
"eslint-plugin-mozilla": "^2.8.0",
Update `npm` packages
2020-10-04 20:49:28 +09:00
"eslint-plugin-no-unsanitized": "^3.1.4",
Update `npm` packages
2020-06-27 18:30:30 +09:00
"eslint-plugin-prettier": "^3.1.4",
Update `npm` packages
2020-05-30 17:58:10 +09:00
"eslint-plugin-unicorn": "^20.1.0",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"globals": "^11.12.0",
"gulp": "^4.0.2",
Update packages
2018-12-23 00:00:53 +09:00
"gulp-postcss": "^8.0.0",
Update packages
2018-08-06 04:20:37 +09:00
"gulp-rename": "^1.4.0",
Update packages
2018-05-20 21:21:08 +09:00
"gulp-replace": "^1.0.0",
Update packages
2018-08-06 04:20:37 +09:00
"gulp-zip": "^4.2.0",
Update Jasmine to version 3.6.1 This is possible now that most intermittent unit test failures have been resolved by other patches. There is only one remaining, but it's very rare and doesn't have to block this update anymore.
2020-08-02 04:11:32 +09:00
"jasmine": "^3.6.1",
Update `npm` packages
2020-09-20 18:34:24 +09:00
"jsdoc": "^3.6.6",
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",
Moves locale and cmaps tasks to gulpfile.
2017-01-11 02:50:38 +09:00
"merge-stream": "^1.0.1",
Update `npm` packages
2020-04-18 18:08:46 +09:00
"mkdirp": "^1.0.4",
Update `npm` packages
2020-09-06 18:49:49 +09:00
"needle": "^2.5.2",
Update `npm` packages
2020-10-04 20:49:28 +09:00
"postcss-calc": "^7.0.5",
Add support for CSS variables using the `PostCSS CSS Variables` package (issue 11462) Having thought *briefly* about using `css-vars-ponyfill`, I'm no longer convinced that it'd be a good idea. The reason is that if we actually want to properly support CSS variables, then that functionality should be available in *all* of our CSS files. Note in particular the `pdf_viewer.css` file that's built as part of the `COMPONENTS` target, in which case I really cannot see how a rewrite-at-the-client solution would ever be guaranteed to always work correctly and without accidentally touching other CSS in the surrounding application. All-in-all, simply re-writing the CSS variables at build-time seems much easier and is thus the approach taken in this patch; courtesy of https://github.com/MadLittleMods/postcss-css-variables By using its `preserve` option, the built files will thus include *both* a fallback and a modern `var(...)` format[1]. As a proof-of-concept this patch removes a couple of manually added fallback values, and converts an additional sidebar related property to use a CSS variable. --- [1] Comparing the `master` branch with this patch, when using `gulp generic`, produces the following diff for the built `web/viewer.css` file: ```diff @@ -408,6 +408,7 @@ :root { --sidebar-width: 200px; + --sidebar-transition-duration: 200ms; } * { @@ -550,27 +551,28 @@ position: absolute; top: 32px; bottom: 0; - width: 200px; /* Here, and elsewhere below, keep the constant value for compatibility - with older browsers that lack support for CSS variables. */ + width: 200px; width: var(--sidebar-width); visibility: hidden; z-index: 100; border-top: 1px solid rgba(51, 51, 51, 1); -webkit-transition-duration: 200ms; transition-duration: 200ms; + -webkit-transition-duration: var(--sidebar-transition-duration); + transition-duration: var(--sidebar-transition-duration); -webkit-transition-timing-function: ease; transition-timing-function: ease; } html[dir='ltr'] #sidebarContainer { -webkit-transition-property: left; transition-property: left; - left: -200px; + left: calc(-1 * 200px); left: calc(-1 * var(--sidebar-width)); } html[dir='rtl'] #sidebarContainer { -webkit-transition-property: right; transition-property: right; - right: -200px; + right: calc(-1 * 200px); right: calc(-1 * var(--sidebar-width)); } @@ -640,6 +642,8 @@ #viewerContainer:not(.pdfPresentationMode) { -webkit-transition-duration: 200ms; transition-duration: 200ms; + -webkit-transition-duration: var(--sidebar-transition-duration); + transition-duration: var(--sidebar-transition-duration); -webkit-transition-timing-function: ease; transition-timing-function: ease; } ```
2020-02-05 06:28:38 +09:00
"postcss-css-variables": "^0.14.0",
Update `npm` packages
2020-09-20 18:34:24 +09:00
"prettier": "^2.1.2",
Upgrade Puppeteer to version 5.3.1
2020-10-04 06:06:31 +09:00
"puppeteer": "^5.3.1",
Update packages
2019-08-25 03:08:09 +09:00
"rimraf": "^2.7.1",
Update all npm packages to the latest versions
2018-01-31 23:51:03 +09:00
"streamqueue": "^1.1.2",
Update `npm` packages
2020-10-04 20:49:28 +09:00
"stylelint": "^13.7.2",
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",
"stylelint-prettier": "^1.1.2",
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
2020-06-27 18:30:30 +09:00
"terser": "^4.8.0",
"through2": "^3.0.2",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"ttest": "^2.1.1",
Add typescript definitions This PR adds typescript definitions from the JSDoc already present. It adds a new gulp-target 'types' that calls 'tsc', the typescript compiler, to create the definitions. To use the definitions, users can simply do the following: ``` import {getDocument, GlobalWorkerOptions} from "pdfjs-dist"; import pdfjsWorker from "pdfjs-dist/build/pdf.worker.entry"; GlobalWorkerOptions.workerSrc = pdfjsWorker; const pdf = await getDocument("file:///some.pdf").promise; ``` Co-authored-by: @oBusk Co-authored-by: @tamuratak
2020-07-23 05:38:04 +09:00
"typescript": "^3.9.7",
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
2020-04-18 18:08:46 +09:00
"web-streams-polyfill": "^2.1.1",
Update `npm` packages
2020-09-20 18:34:24 +09:00
"webpack": "^4.44.2",
Update the `webpack-stream` dependency (issue 11996) Given that the long-standing `webpack-stream` issue 201 was recently fixed in PR 207, and a new version released, we should now finally be able to update the dependency. However, depending on if/when `webpack-stream` gets support for Webpack 5 (which is currently in beta) we may still want remove our `webpack-stream` dependency.
2020-09-20 20:42:16 +09:00
"webpack-stream": "~6.1.0",
Update packages
2018-11-25 05:00:22 +09:00
"wintersmith": "^2.5.0",
Update packages
2019-10-18 23:42:02 +09:00
"yargs": "^11.1.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