interesting
/
PeerTube
mirror of https://github.com/Chocobozzz/PeerTube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
PeerTube/apps/peertube-runner/package.json

22 lines
492 B
JSON
Raw Normal View History

Add peertube runner cli
2023-04-21 08:05:27 -05:00
{
Use @peertube org for npm
2023-05-09 03:16:18 -05:00
"name": "@peertube/peertube-runner",
Update runner version
2024-04-04 09:32:44 -05:00
"version": "0.0.16",
Migrate server to ESM Sorry for the very big commit that may lead to git log issues and merge conflicts, but it's a major step forward: * Server can be faster at startup because imports() are async and we can easily lazy import big modules * Angular doesn't seem to support ES import (with .js extension), so we had to correctly organize peertube into a monorepo: * Use yarn workspace feature * Use typescript reference projects for dependencies * Shared projects have been moved into "packages", each one is now a node module (with a dedicated package.json/tsconfig.json) * server/tools have been moved into apps/ and is now a dedicated app bundled and published on NPM so users don't have to build peertube cli tools manually * server/tests have been moved into packages/ so we don't compile them every time we want to run the server * Use isolatedModule option: * Had to move from const enum to const (https://www.typescriptlang.org/docs/handbook/enums.html#objects-vs-enums) * Had to explictely specify "type" imports when used in decorators * Prefer tsx (that uses esbuild under the hood) instead of ts-node to load typescript files (tests with mocha or scripts): * To reduce test complexity as esbuild doesn't support decorator metadata, we only test server files that do not import server models * We still build tests files into js files for a faster CI * Remove unmaintained peertube CLI import script * Removed some barrels to speed up execution (less imports)
2023-07-31 07:34:36 -05:00
"type": "module",
Add peertube runner cli
2023-04-21 08:05:27 -05:00
"main": "dist/peertube-runner.js",
Breaking: remove node 14 support
2023-05-09 03:00:52 -05:00
"bin": "dist/peertube-runner.js",
Migrate server to ESM Sorry for the very big commit that may lead to git log issues and merge conflicts, but it's a major step forward: * Server can be faster at startup because imports() are async and we can easily lazy import big modules * Angular doesn't seem to support ES import (with .js extension), so we had to correctly organize peertube into a monorepo: * Use yarn workspace feature * Use typescript reference projects for dependencies * Shared projects have been moved into "packages", each one is now a node module (with a dedicated package.json/tsconfig.json) * server/tools have been moved into apps/ and is now a dedicated app bundled and published on NPM so users don't have to build peertube cli tools manually * server/tests have been moved into packages/ so we don't compile them every time we want to run the server * Use isolatedModule option: * Had to move from const enum to const (https://www.typescriptlang.org/docs/handbook/enums.html#objects-vs-enums) * Had to explictely specify "type" imports when used in decorators * Prefer tsx (that uses esbuild under the hood) instead of ts-node to load typescript files (tests with mocha or scripts): * To reduce test complexity as esbuild doesn't support decorator metadata, we only test server files that do not import server models * We still build tests files into js files for a faster CI * Remove unmaintained peertube CLI import script * Removed some barrels to speed up execution (less imports)
2023-07-31 07:34:36 -05:00
"engines": {
"node": ">=16.x"
},
Add peertube runner cli
2023-04-21 08:05:27 -05:00
"license": "AGPL-3.0",
Fix peertube-runner with node >= 20.11 See https://github.com/Chocobozzz/PeerTube/issues/6171
2024-01-19 03:53:57 -06:00
"dependencies": {},
Add peertube runner cli
2023-04-21 08:05:27 -05:00
"devDependencies": {
"@iarna/toml": "^2.2.5",
Fix peertube-runner with node >= 20.11 See https://github.com/Chocobozzz/PeerTube/issues/6171
2024-01-19 03:53:57 -06:00
"@peertube/net-ipc": "^2.2.0",
Runner download videoFileUrl follow redirect The runner downloads the video file from the url set in the paylaod of a transcoding job. This url is pointing to our API and the runner will make POST request to it with an jobToken and a runnerToken. Doing this ensure we can verify the tokens and return the video file. But returning the video file also means that we are using server resources to serve the file. If the runner is able to follow the redirect, we can do our usual verification and return a redirect response to the url of the video file, the runner will download it using his own resources.
2023-12-19 09:02:00 -06:00
"@types/follow-redirects": "1.14.4",
Add peertube runner cli
2023-04-21 08:05:27 -05:00
"env-paths": "^3.0.0",
Fix peertube-runner with node >= 20.11 See https://github.com/Chocobozzz/PeerTube/issues/6171
2024-01-19 03:53:57 -06:00
"follow-redirects": "^1.15.5",
Update apps dependencies
2024-06-21 07:49:17 -05:00
"pino": "^9.2.0",
"pino-pretty": "^11.2.1"
Add peertube runner cli
2023-04-21 08:05:27 -05:00
}
}