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

66 lines
1.8 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-01-31 22:04:49 +09:00
"@babel/core": "^7.8.4",
"@babel/plugin-transform-modules-commonjs": "^7.8.3",
"@babel/plugin-transform-runtime": "^7.8.3",
"@babel/preset-env": "^7.8.4",
"@babel/runtime": "^7.8.4",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"acorn": "^6.4.0",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"autoprefixer": "^9.7.4",
Update packages This includes a major upgrade of `terser`.
2019-05-25 23:36:42 +09:00
"babel-loader": "^8.0.6",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"canvas": "^2.6.1",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"core-js": "^3.6.4",
"escodegen": "^1.13.0",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"eslint": "^6.8.0",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"eslint-config-prettier": "^6.10.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",
"eslint-plugin-html": "^6.0.0",
Update `npm` packages
2020-01-31 22:04:49 +09:00
"eslint-plugin-import": "^2.20.0",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"eslint-plugin-mozilla": "^2.3.1",
Update packages
2018-05-20 21:21:08 +09:00
"eslint-plugin-no-unsanitized": "^3.0.2",
Update `npm` packages
2019-12-19 19:28:13 +09:00
"eslint-plugin-prettier": "^3.1.2",
Upgrade to `eslint` version 6 This major version bump required two changes: - The global line in the mobile viewer example should be removed because the `.eslintrc` file already defines these globals and with the new `eslint` version we otherwise get an error saying "'pdfjsLib' is already defined as a built-in global variable". - The ECMA version for the examples must be set to 6 since we're using modules, otherwise we get an error saying "sourceType 'module' is not supported when ecmaVersion < 2015". It turns out that the previous version of `eslint` already used ECMA version 6 silently even though we set 5, see https://github.com/eslint/eslint/issues/9687#issuecomment-432413384, so in terms of our code nothing really changes.
2019-08-25 03:21:10 +09:00
"eslint-plugin-unicorn": "^10.0.0",
Update packages
2018-12-23 00:00:53 +09:00
"fancy-log": "^1.3.3",
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 translations and packages
2019-09-21 20:41:59 +09:00
"jasmine": "^3.5.0",
"jasmine-core": "^3.5.0",
Update packages
2019-08-25 03:08:09 +09:00
"jsdoc": "^3.6.3",
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",
Gulp: port the `all`, `extension` and `jsdoc` targets This requires the `run-sequence` dependency because Gulp does not have a way to run sequences of tasks inside a Gulp task. Gulp 4.0 will have support for this, but until that is released this is the recommended way to implement it.
2016-10-16 23:06:37 +09:00
"mkdirp": "^0.5.1",
Update the left/right CSS calculation for the `sidebarContainer` HTML element to enable IE11 compatibility As gross as this hack is, it nonetheless seem necessary to allow using CSS variables; see also https://github.com/mozilla/pdf.js/pull/11567#issuecomment-582166160
2020-02-05 08:34:44 +09:00
"postcss-calc": "^7.0.1",
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
2019-11-11 19:22:03 +09:00
"prettier": "^1.19.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 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-01-31 22:04:49 +09:00
"terser": "^4.6.3",
added transform function added depedencies removed gulp-transform dependency removed dependencies removed gulptransform dependency
2019-11-13 11:51:31 +09:00
"through2": "^3.0.1",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"ttest": "^2.1.1",
Update packages
2018-07-01 03:39:31 +09:00
"typogr": "^0.6.8",
"vinyl": "^2.2.0",
Update packages
2018-05-20 21:21:08 +09:00
"vinyl-fs": "^3.0.3",
Update npm packages
2019-11-11 19:22:03 +09:00
"web-streams-polyfill": "^2.0.6",
Update `npm` packages
2019-12-29 03:57:25 +09:00
"webpack": "^4.41.5",
Update webpack-stream to fix vulnerabiliy reported by npm https://npmjs.com/advisories/1084 webpack-stream between 4.0.3 and 5.0.0 added official support for Webpack 4. Which is nice since we ARE using Webpack 4... Also, dropped support for Node.js 4 which shouldn't be a big deal for us since we are already using packages that are incompatible with Node.js 4 (Webpack 4.x supports Node.js 6 and up).
2019-12-23 02:36:06 +09:00
"webpack-stream": "~5.0.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": {
Re-factor the `npm test` command, used by Travis, to avoid running the 'default_preferences' tasks concurrently (issue 10732) *Please note:* This patch does *not* prevent the 'default_preferences' task from running more than once during `npm test`, but it does ensure that the tasks won't run *concurrently* by running the relevant tests in *series*. While it would obviously still make sense to re-factor the gulpfile to account for changes in `gulp` version 4, by at least tweaking the `npm test` command the intermittent failures on Travis should at least go away.
2019-12-19 05:26:44 +09:00
"test": "env SKIP_BABEL=true 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