libre-service.eu/pad.libre-service.eu-etherpad
libre-service.eu/pad.libre-service.eu-etherpad
1
0
Fork 0
mirror of https://github.com/ether/etherpad-lite.git synced 2025-01-21 06:52:46 +01:00
Code Issues Projects Releases Wiki Activity
pad.libre-service.eu-etherpad/src/package.json

91 lines
2 KiB
JSON
Raw Normal View History

Added a package.json, now installable via 'npm ep-lite' and startable via 'ep-lite'. Fixed #6
2011-05-08 20:10:42 +02:00
{
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"name": "ep_etherpad-lite",
readme: language revision. Removed stale info. Tried to simplify the document, to reduce unneded info, and to use a less informal language. For example, the introductory links describing git made sense 10 years ago. Today they are not needed to understand what Etherpad is. And mercurial was always better than git, anyways :) The mailing list and the IRC channel seem pretty dead by now. Let's just move everything to Github issues, which was the de facto situation anyways. About the donation links: I am the maintainer, and I do not know the identity of the owners of the donation links, so it is correct to remove them. The same was done on the website three months ago: https://github.com/ether/ether.github.com/commit/d4ef04605da5
2019-10-20 00:40:18 +02:00
"description": "A free and open source realtime collaborative editor",
Change everywhere the link to https://etherpad.org (it was plain http)
2019-04-16 00:54:54 +02:00
"homepage": "https://etherpad.org",
package.json: last reformatting These are the remaining non-whitespace changes needed to normalize package.json formatting, bringing it in line with the npm 6.1.0 default format. Future edits to this file should follow this default format, in order to minimize churn.
2018-07-14 14:58:38 +02:00
"keywords": [
"etherpad",
"realtime",
"collaborative",
"editor"
],
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"author": "Etherpad Foundation",
"contributors": [
package.json: last reformatting These are the remaining non-whitespace changes needed to normalize package.json formatting, bringing it in line with the npm 6.1.0 default format. Future edits to this file should follow this default format, in order to minimize churn.
2018-07-14 14:58:38 +02:00
{
"name": "John McLear"
},
package.json: list myself among the authors
2019-01-26 00:11:11 +01:00
{
"name": "Antonio Muci"
},
package.json: last reformatting These are the remaining non-whitespace changes needed to normalize package.json formatting, bringing it in line with the npm 6.1.0 default format. Future edits to this file should follow this default format, in order to minimize churn.
2018-07-14 14:58:38 +02:00
{
"name": "Hans Pinckaers"
},
{
"name": "Robin Buse"
},
{
"name": "Marcel Klehr"
},
{
"name": "Peter Martischka"
}
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
],
"dependencies": {
"async": "0.9.0",
"async-stacktrace": "0.0.2",
"channels": "0.0.4",
"cheerio": "0.20.0",
minify: upgrade clean-css 3.4.19 -> 4.2.3. Adapt to the semver major change CleanCSS 3.4.19 had a Regex Denial of Service vulnerability and has to be updated. The major version bump requires the following changes: 1. Disabling rebase is necessary because otherwise the URLs for the web fonts become wrong; EXAMPLE 1: /static/css/src/static/font/fontawesome-etherpad.woff instead of /static/font/fontawesome-etherpad.woff EXAMPLE 2 (this is more surprising): /p/src/static/font/opendyslexic.otf instead of /static/font/opendyslexic.otf 2. CleanCSS.minify() can either receive a string containing the CSS, or an array of strings. In that case each array element is interpreted as an absolute local path from which the CSS file is read. In version 4.x, CleanCSS API was simplified, eliminating the relativeTo parameter, and thus we cannot use our already loaded "content" argument, but we have to wrap the absolute path to the CSS in an array and ask the library to read it by itself. Fixes #3616.
2020-03-22 00:33:22 +01:00
"clean-css": "4.2.3",
dependencies: update cookie-parser, 1.4.3 -> 1.4.4 This is a non breaking change. From the changelog (https://github.com/expressjs/cookie-parser/blob/1.4.4/HISTORY.md#144--2019-02-12): # 1.4.4 / 2019-02-12 - perf: normalize secret argument only once
2019-05-04 16:49:33 +02:00
"cookie-parser": "1.4.4",
dependencies: update ejs, 2.5.7 -> 2.6.1
2018-10-17 00:31:55 +02:00
"ejs": "2.6.1",
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"etherpad-require-kernel": "1.0.9",
"etherpad-yajsml": "0.0.2",
dependencies: upgrade express 4.16.4 -> 4.17.1 This upgrade should be backward compatible. Changelogs: - https://expressjs.com/en/changelog/4x.html - https://github.com/expressjs/express/blob/master/History.md#4171--2019-05-25 4.17.1 - Release date: 2019-05-25 The 4.17.1 patch release includes one bug fix: The change to the res.status() API has been reverted due to causing regressions in existing Express 4 applications. 4.17.0 - Release date: 2019-05-16 The 4.17.0 minor release includes bug fixes and some new features, including: The express.raw() and express.text() middleware have been added to provide request body parsing for more raw request payloads. This uses the expressjs/body-parser module module underneath, so apps that are currently requiring the module separately can switch to the built-in parsers. The res.cookie() API now supports the "none" value for the sameSite option. When the "trust proxy" setting is enabled, the req.hostname now supports multiple X-Forwarded-For headers in a request. Starting with this version, Express supports Node.js 10.x and 12.x. The res.sendFile() API now provides and more immediate and easier to understand error when a non-string is passed as the path argument. The res.status() API now provides and more immediate and easier to understand error when null or undefined is passed as the argument.
2019-10-20 01:29:26 +02:00
"express": "4.17.1",
dependencies: upgrade express-session 1.16.1 -> 1.17.0 This upgrade should be backward compatible. Changelog: - https://github.com/expressjs/session/blob/master/HISTORY.md 1.17.0 / 2019-10-10 deps: cookie@0.4.0 Add SameSite=None support deps: safe-buffer@5.2.0 1.16.2 / 2019-06-12 Fix restoring cookie.originalMaxAge when store returns Date deps: parseurl@~1.3.3
2019-10-20 01:32:12 +02:00
"express-session": "1.17.0",
AbsolutePaths: written findEtherpadRoot() This is just a function (with an ugly side effect for caching purposes) that heuristically tries to compute the Etherpad installation path when running under Unix and win32 (they have different file system layouts). This path can be used by Etherpad as a base for all the relative paths, in order to be deterministic and not depending on cwd.
2018-08-22 00:38:13 +02:00
"find-root": "1.1.0",
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"formidable": "1.2.1",
dependencies: upgrade graceful-fs 4.1.15 -> 4.2.2 Without this, on nodejs 10 and 12 (and maybe 8, not tested), Etherpad failed to start, throwing the following error: [2019-10-22 19:01:01.439] [ERROR] console - exception thrown: Maximum call stack size exceeded [2019-10-22 19:01:01.439] [INFO] console - RangeError: Maximum call stack size exceeded at Function.[Symbol.hasInstance] (<anonymous>) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:194:14) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:195:28) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:195:28) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:195:28) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:195:28) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:195:28) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:195:28) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:195:28) at ReadStream (/opt/etherpad-lite/src/node_modules/graceful-fs/graceful-fs.js:195:28) Fixes #3654.
2019-10-22 21:59:37 +02:00
"graceful-fs": "4.2.2",
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"jsonminify": "0.4.1",
"languages4translatewiki": "0.1.3",
"log4js": "0.6.35",
dependencies: updated measured 1.1.0 -> measured-core 1.11.2 When installing dependencies, npm informed us that measured had been deprecated, and renamed to measured-core. Let's follow the advice, and get rid of the warning. npm WARN deprecated measured@1.1.0: This package has been renamed to measured-core, all versions of measured have been re-released under measured-core, please update your package and consider updating to the newest version. See https://github.com/yaorg/node-measured for latest updates. This package is used to expose a single endpoint ("/stats"), whose output does not change after this commit. Fixes #3458
2018-08-14 13:22:41 +02:00
"measured-core": "1.11.2",
PadMessageHandler.js: convert handleUserChanges() to Promises - the call site still expects a nodeback function, so also introduced the `nodeify` module to allow that function to work as expected.
2019-01-30 11:43:01 +01:00
"nodeify": "^1.0.1",
dependencies: upgrade npm 6.13.1 -> 6.13.4 This fixes some security vulnerabilites, among them an arbitrary file overwrite. The output of `npm audit` goes from this: found 17 vulnerabilities (15 low, 2 high) in 13344 scanned packages run `npm audit fix` to fix 6 of them. 1 vulnerability requires semver-major dependency updates. 10 vulnerabilities require manual review. See the full report for details. To this: found 5 vulnerabilities (3 low, 2 high) in 13370 scanned packages 1 vulnerability requires semver-major dependency updates. 4 vulnerabilities require manual review. See the full report for details. Changelog: - https://github.com/npm/cli/releases 6.13.4 (2019-12-11) BUGFIXES 320ac9aee npm/bin-links#12 npm/gentle-fs#7 Do not remove global bin/man links inappropriately (@isaacs) DEPENDENCIES 52fd21061 gentle-fs@2.3.0 (@isaacs) d06f5c0b0 bin-links@1.1.6 (@isaacs) 6.13.3 (2019-12-09) DEPENDENCIES 19ce061a2 bin-links@1.1.5 Properly normalize, sanitize, and verify bin entries in package.json. 59c836aae npm-packlist@1.4.7 fb4ecd7d2 pacote@9.5.11 5f33040 #476 npm/pacote#22 npm/pacote#14 fix: Do not drop perms in git when not root (isaacs, @darcyclarke) 6f229f7 sanitize and normalize package bin field (isaacs) 1743cb339 read-package-json@2.1.1 6.13.2 (2019-12-03) BUG FIXES 4429645b3 #546 fix docs target typo (@richardlau) 867642942 #142 fix(packageRelativePath): fix 'where' for file deps (@larsgw) d480f2c17 #527 Revert "windows: Add preliminary WSL support for npm and npx" (@craigloewen-msft) e4b97962e #504 remove unnecessary package.json read when reading shrinkwrap (@Lighting-Jack) 1c65d26ac #501 fix(fund): open url for string shorthand (@ruyadorno) ae7afe565 #263 Don't log error message if git tagging is disabled (@woppa684) 4c1b16f6a #182 Warn the user that it is uninstalling npm-install (@Hoidberg)
2019-12-18 01:17:35 +01:00
"npm": "6.13.4",
runtime: polyfill Object.values() Minimum supported Node version is 6.9.0, but Object.values() was introduced in Node < 7. Let's use a polyfill if needed. This will be removed when minimum supported Node version is raised to 8.9.0. Fixes #3459
2018-08-15 22:34:05 +02:00
"object.values": "^1.0.4",
dependencies: update request, 2.83.0 -> 2.88.0
2018-10-17 00:27:51 +02:00
"request": "2.88.0",
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"resolve": "1.1.7",
"security": "1.0.0",
dependencies: update semver, 5.1.0 -> 5.6.0
2018-10-17 00:28:21 +02:00
"semver": "5.6.0",
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"slide": "1.1.6",
dependencies: update socket.io 1.7.3 -> 2.1.1 Version 2.x is not backwards compatible with 1.x. However, according to [0], [1] and [2], it seems that the biggest concern is when mixing different server and client versions, and this is not Etherpad's case. Smoke tested (successfully) on Firefox 61, Chromium 68. npm audit before this change: found 12 vulnerabilities (9 low, 3 high) in 8205 scanned packages 11 vulnerabilities require semver-major dependency updates. 1 vulnerability requires manual review. See the full report for details. npm audit after this change: found 1 low severity vulnerability in 8196 scanned packages 1 vulnerability requires manual review. See the full report for details. Fixes #3462 [0] https://socket.io/blog/socket-io-2-0-0/ [1] https://github.com/socketio/socket.io/issues/3007#issuecomment-336791836 [2] https://github.com/Enalean/tuleap/commit/a0d7a794ded03a0001d2164cb25a9e26b5441a89
2018-08-18 19:42:42 +02:00
"socket.io": "2.1.1",
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"swagger-node-express": "2.1.3",
"tinycon": "0.0.1",
Update package.json
2018-07-20 18:54:48 +02:00
"ueberdb2": "0.4.0",
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"uglify-js": "2.6.2",
"underscore": "1.8.3",
"unorm": "1.4.1"
Update Deps https://i.imgur.com/cxFXNeY.png
2018-03-23 14:21:59 +01:00
},
package.json: last reformatting These are the remaining non-whitespace changes needed to normalize package.json formatting, bringing it in line with the npm 6.1.0 default format. Future edits to this file should follow this default format, in order to minimize churn.
2018-07-14 14:58:38 +02:00
"bin": {
"etherpad-lite": "./node/server.js"
},
Added a jshint binary
2012-01-22 14:56:08 +01:00
"devDependencies": {
tests: update mocha 5.0.5 -> 5.2.0 This does not break any backend tests
2018-07-28 01:02:43 +02:00
"mocha": "5.2.0",
dependencies: update nyc, 12.0.1 -> 14.1.0 This is just a dev dependency, so no real risks, but it's better not to scare users. Reported vulnerability before this change: $ npm audit === npm audit security report === # Run npm install --save-dev nyc@14.1.0 to resolve 1 vulnerability SEMVER WARNING: Recommended action is a potentially breaking change ┌───────────────┬──────────────────────────────────────────────────────────────┐ │ High │ Prototype Pollution │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Package │ handlebars │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Dependency of │ nyc [dev] │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ Path │ nyc > istanbul-reports > handlebars │ ├───────────────┼──────────────────────────────────────────────────────────────┤ │ More info │ https://nodesecurity.io/advisories/755 │ └───────────────┴──────────────────────────────────────────────────────────────┘
2019-05-03 23:27:35 +02:00
"nyc": "14.1.0",
tests: move supertest among devDependencies in package.json
2018-07-27 22:30:20 +02:00
"supertest": "3.0.0",
dependencies: upgrade wd 1.11.3 -> 1.11.4 This is just a dev dependency.
2019-10-20 01:34:44 +02:00
"wd": "1.11.4"
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
},
package.json: last reformatting These are the remaining non-whitespace changes needed to normalize package.json formatting, bringing it in line with the npm 6.1.0 default format. Future edits to this file should follow this default format, in order to minimize churn.
2018-07-14 14:58:38 +02:00
"engines": {
node8: require nodejs >= 8.9.0, npm >= 6.4 Next version will be Etherpad 1.8. As planned in #3424, we are going to require NodeJS >=8.9.0 and npm >= 6.4. This commit implements that change and updates documentation and scripts. Subsequent changes will get rid of old idioms, dating back to node < 0.7, that still survive in the code. Once migrated to NodeJS 8, we will be able to start working on migrating the code base from callbacks to async/await, greatly simplifying legibility (see #3540). Closes #3557
2019-02-19 00:48:50 +01:00
"node": ">=8.9.0",
package.json: reduced npm minimum version here, too (6.4.1 -> 5.5.1) This should really have been part of 4f753809fe13.
2019-10-20 01:06:34 +02:00
"npm": ">=5.5.1"
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
},
package.json: last reformatting These are the remaining non-whitespace changes needed to normalize package.json formatting, bringing it in line with the npm 6.1.0 default format. Future edits to this file should follow this default format, in order to minimize churn.
2018-07-14 14:58:38 +02:00
"repository": {
"type": "git",
package.json: "http://github.com" -> "https://github.com"
2019-01-26 00:12:16 +01:00
"url": "https://github.com/ether/etherpad-lite.git"
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
},
tests: backend tests are now run with "npm test" instead of a custom bash script
2018-07-28 00:26:39 +02:00
"scripts": {
ci: test basic application response of the docker build Note by muxator: This commit introduced a copied & modified version of the testing files loadSettings.js and pad.js. It's Christmas night, and we want to shipt this feature, so I merged it anyway, adding a note in both the original and copied files so that hopefully someone in the distant future is going to merge them back again.
2019-12-03 23:14:00 +01:00
"test": "nyc mocha --timeout 5000 ../tests/backend/specs/api",
"test-container": "nyc mocha --timeout 5000 ../tests/container/specs/api"
tests: backend tests are now run with "npm test" instead of a custom bash script
2018-07-28 00:26:39 +02:00
},
release: prepare for 1.8.0
2019-12-07 18:55:07 +01:00
"version": "1.8.0",
package.json: whitespace changes Only cosmetic changes to make it easier to understand what changes in the other commits. This command: git diff this-commit-hash^! --ignore-all-space should give an empty output on this commit.
2018-07-14 14:44:48 +02:00
"license": "Apache-2.0"
Added a package.json, now installable via 'npm ep-lite' and startable via 'ep-lite'. Fixed #6
2011-05-08 20:10:42 +02:00
}
Reference in a new issue Copy permalink