OpenCloud
/
riot-web
mirror of https://github.com/vector-im/riot-web
1
0
Fork 0
Code Issues Releases Wiki Activity
riot-web/package.json

193 lines
7.4 KiB
JSON
Raw Normal View History

Basic structure of a react SDK and start of an implementation.
2015-06-09 18:40:42 +02:00
{
Update name & repo to reflect renamed repository Unsure whether we want to go through doing a complete s/vector/riot/ - I'm not sure there's a whole lot of point.
2016-12-05 15:40:06 +01:00
"name": "riot-web",
Electron support From https://github.com/vector-im/vector-web/pull/2511 but with just the actual electron changes
2016-11-02 19:49:28 +01:00
"productName": "Riot",
npm is "smart" enough to try and install our electron wrapper as a module instead of the actual electron package. With no way to ignore directories. I'd like to think of this as temporary, until I get to rip apart riot-web and riot-electron Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-10 14:36:27 +02:00
"main": "electron_app/src/electron-main.js",
v1.3.1-rc.1
2019-07-31 17:55:49 +02:00
"version": "1.3.1-rc.1",
Electron support From https://github.com/vector-im/vector-web/pull/2511 but with just the actual electron changes
2016-11-02 19:49:28 +01:00
"description": "A feature-rich client for Matrix.org",
Change author
2018-01-08 22:32:25 +01:00
"author": "New Vector Ltd.",
Add repository fields to package.json and add a README to the example
2015-06-09 19:52:26 +02:00
"repository": {
"type": "git",
Update name & repo to reflect renamed repository Unsure whether we want to go through doing a complete s/vector/riot/ - I'm not sure there's a whole lot of point.
2016-12-05 15:40:06 +01:00
"url": "https://github.com/vector-im/riot-web"
Add repository fields to package.json and add a README to the example
2015-06-09 19:52:26 +02:00
},
Tweak the example build process. Move example -> examples/trivial to we can have more than one. Update README appropriately.
2015-07-03 16:56:04 +02:00
"license": "Apache-2.0",
Don't include the world in the published packages We ended up including all sorts of stuff in our published packages. Let's take the opposite approach and include useful stuff rather than exclude unuseful stuff.
2016-10-26 16:35:54 +02:00
"files": [
"AUTHORS.rst",
"CONTRIBUTING.rst",
"deploy",
"docs",
"karma.conf.js",
"lib",
"release.sh",
"scripts",
"src",
"test",
"webpack.config.js"
],
Tweak the example build process. Move example -> examples/trivial to we can have more than one. Update README appropriately.
2015-07-03 16:56:04 +02:00
"style": "bundle.css",
WIP of component indexing update
2015-11-30 18:31:32 +01:00
"matrix-react-parent": "matrix-react-sdk",
Basic structure of a react SDK and start of an implementation.
2015-06-09 18:40:42 +02:00
"scripts": {
Move copyright header
2015-11-30 19:00:54 +01:00
"reskindex": "reskindex -h src/header",
Automatically update component-index Following changes to the react-sdk, reskindex can now be updated using the "-w" (watch) equivalent of the reskindex script. -Alter npm scripts so that reskindex is run when building once and so that reskindex:start is runwhen developing -Remove and stop tracking component-index, this will now only be created at build-time
2017-05-11 11:35:56 +02:00
"reskindex:watch": "reskindex -h src/header -w",
Switch to gen-i18n script
2017-10-19 11:53:02 +02:00
"i18n": "matrix-gen-i18n",
Add script to prune unused translations
2017-10-19 13:11:53 +02:00
"prunei18n": "matrix-prune-i18n",
Verify i18n in CI
2019-07-11 20:45:06 +02:00
"diff-i18n": "cp src/i18n/strings/en_EN.json src/i18n/strings/en_EN_orig.json && yarn i18n && node scripts/compare-file.js src/i18n/strings/en_EN_orig.json src/i18n/strings/en_EN.json",
Use a custom script to copy resources (#2893) All of those cpx invocations were getting unwieldy, and I suspect the exotic quoting needed to run them under parallelshell was breaking things on windows. Replace the unwieldy cpx invocations with an unwieldy custom script.
2017-01-06 11:43:13 +01:00
"build:res": "node scripts/copy-res.js",
Use Modernizr to check for browser compatibility Add a CompatibilityPage which is shown for incompatible clients. If they continue on regardless, proceed as if it never happened.
2015-10-28 18:39:50 +01:00
"build:modernizr": "modernizr -c .modernizr.json -d src/vector/modernizr.js",
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best.
2019-03-12 12:06:57 +01:00
"build:compile": "yarn reskindex && babel --source-maps -d lib src",
Process images with Webpack This adds a `file-loader` rule to the Webpack build so that any requests for image resource will be output into the app's output directory, but with an extra content has appended so that we can safely use a long cache lifetime. The CSS and SCSS rules are also changed to use `css-loader` so that any `url` inside is automatically processed by the new image rule above.
2019-01-01 00:22:47 +01:00
"build:bundle": "cross-env NODE_ENV=production webpack -p --progress --bail --mode production",
"build:bundle:dev": "webpack --progress --bail --mode development",
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best.
2019-03-12 12:06:57 +01:00
"build:electron": "yarn clean && yarn build && yarn install:electron && build -wml --ia32 --x64",
Remove 32-bit builds for MacOS and Linux
2019-04-09 19:24:30 +02:00
"build:electron:linux": "yarn build && build -l --x64",
"build:electron:macos": "yarn build && build -m --x64",
Switch to yarn
2019-04-09 18:03:58 +02:00
"build:electron:windows": "yarn build && build -w --ia32 --x64",
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best.
2019-03-12 12:06:57 +01:00
"build:react-sdk": "node scripts/yarn-sub.js matrix-react-sdk build",
"build:js-sdk": "node scripts/yarn-sub.js matrix-js-sdk start:init",
"build": "yarn build:js-sdk && yarn build:react-sdk && yarn reskindex && yarn build:res && yarn build:bundle",
"build:dev": "yarn build:js-sdk && yarn build:react-sdk && yarn reskindex && yarn build:res && yarn build:bundle:dev",
Rename the package script/output dir to 'dist' To match conventions from other projects and match the release script which expects releasde artefacts in dist/
2016-11-01 16:22:06 +01:00
"dist": "scripts/package.sh",
Convert install-app-deps to subcommand
2019-07-12 18:02:12 +02:00
"install:electron": "electron-builder install-app-deps",
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best.
2019-03-12 12:06:57 +01:00
"electron": "yarn install:electron && electron .",
Use a custom script to copy resources (#2893) All of those cpx invocations were getting unwieldy, and I suspect the exotic quoting needed to run them under parallelshell was breaking things on windows. Replace the unwieldy cpx invocations with an unwieldy custom script.
2017-01-06 11:43:13 +01:00
"start:res": "node scripts/copy-res.js -w",
Allow Webpack dev server to listen to all interfaces Signed-off-by: J. Ryan Stinnett <jryans@gmail.com>
2018-11-08 20:55:51 +01:00
"start:js": "webpack-dev-server --host=0.0.0.0 --output-filename=bundles/_dev_/[name].js --output-chunk-filename=bundles/_dev_/[name].js -w --progress --mode development",
Swap out the complicated canary stuff for serial execution Fixes https://github.com/vector-im/riot-web/issues/7386
2018-09-25 23:49:14 +02:00
"start:js:prod": "cross-env NODE_ENV=production webpack-dev-server -w --progress",
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best.
2019-03-12 12:06:57 +01:00
"start:js-sdk": "node scripts/yarn-sub.js matrix-js-sdk start:watch",
"start:js-sdk:prod": "cross-env NODE_ENV=production node scripts/yarn-sub.js matrix-js-sdk start:watch",
"start:react-sdk": "node scripts/yarn-sub.js matrix-react-sdk start:all",
"start:react-sdk:prod": "cross-env NODE_ENV=production node scripts/yarn-sub.js matrix-react-sdk start:all",
"start": "yarn build:js-sdk && yarn build:react-sdk && concurrently --kill-others-on-fail --prefix \"{time} [{name}]\" -n js-sdk,react-sdk,reskindex,res,riot-js \"yarn start:js-sdk\" \"yarn start:react-sdk\" \"yarn reskindex:watch\" \"yarn start:res\" \"yarn start:js\"",
"start:prod": "yarn build:js-sdk && yarn build:react-sdk && concurrently --kill-others-on-fail --prefix \"{time} [{name}]\" -n js-sdk,react-sdk,reskindex,res,riot-js \"yarn start:js-sdk:prod\" \"yarn start:react-sdk:prod\" \"yarn reskindex:watch\" \"yarn start:res\" \"yarn start:js:prod\"",
Add eslint config An early start that gets some linting in place.
2017-01-23 15:22:54 +01:00
"lint": "eslint src/",
"lintall": "eslint src/ test/",
change electron -> electron_app which was previously missed Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-06-06 19:39:54 +02:00
"clean": "rimraf lib webapp electron_app/dist",
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best.
2019-03-12 12:06:57 +01:00
"prepare": "yarn clean && yarn build:compile",
Set up BuildKite for Chrome
2019-03-14 02:46:52 +01:00
"test": "karma start --single-run=true --autoWatch=false --browsers VectorChromeHeadless",
Refactor karma config - rename test:multi npm target to test-multi, for consistency with react-sdk - base karma webpack config on the distribution one - include Olm if we have it - don't use the karma source loader - it's pointless given we webpack everything. - turn off module listing in the webpack stats to shorten the console output
2017-02-03 00:31:22 +01:00
"test-multi": "karma start"
Basic structure of a react SDK and start of an implementation.
2015-06-09 18:40:42 +02:00
},
"dependencies": {
upgrade karma & babel to latest
2018-09-26 03:27:22 +02:00
"babel-polyfill": "^6.26.0",
"babel-runtime": "^6.26.0",
Actually update package.json
2018-09-28 12:02:14 +02:00
"bluebird": "^3.5.2",
serve config.json statically instead of bundling it issue #1344
2016-05-25 02:08:09 +02:00
"browser-request": "^0.3.3",
Fix dependencies to the same versions as react-sdk Otherwise Things Get Weird, eg. headers in the left panel end up in the wrong place because the gemini scrollbar CSS has changed between versions.
2018-04-26 16:25:20 +02:00
"draft-js": "^0.11.0-alpha",
find versions of webpack, webpack-cli, and karma-webpack which work together atm
2018-09-26 02:18:53 +02:00
"extract-text-webpack-plugin": "^4.0.0-beta.0",
Implement Platforms Provide WebPlatform for functionality specific to the web version of vector.
2016-11-02 16:12:51 +01:00
"favico.js": "^0.3.10",
Update a bunch of deps To try & get deps without vulns in them. Exceptions are: * electron builder: which is nontrivial to update * webpack-dev-server: probably needs newer webpack * moderizr: no new version released yet
2018-09-26 13:33:53 +02:00
"gemini-scrollbar": "github:matrix-org/gemini-scrollbar#b302279",
"gfm.css": "^1.1.2",
npm update
2018-10-29 15:30:35 +01:00
"highlight.js": "^9.13.1",
Released js-sdk & react-sdk
2019-08-05 13:04:57 +02:00
"matrix-js-sdk": "2.3.0",
"matrix-react-sdk": "1.5.0",
Update a bunch of deps To try & get deps without vulns in them. Exceptions are: * electron builder: which is nontrivial to update * webpack-dev-server: probably needs newer webpack * moderizr: no new version released yet
2018-09-26 13:33:53 +02:00
"modernizr": "^3.6.0",
use the release version of olm 3.1.0
2019-04-24 00:08:07 +02:00
"olm": "https://packages.matrix.org/npm/olm/olm-3.1.0.tgz",
Update a bunch of deps To try & get deps without vulns in them. Exceptions are: * electron builder: which is nontrivial to update * webpack-dev-server: probably needs newer webpack * moderizr: no new version released yet
2018-09-26 13:33:53 +02:00
"prop-types": "^15.6.2",
Bump react to 15.6 to fix build problems matrix-react-test-tools requires react 15.6 or later, so make sure we require it in riot-web too.
2017-07-14 15:45:44 +02:00
"react": "^15.6.0",
"react-dom": "^15.6.0",
update deps
2018-10-16 12:12:13 +02:00
"sanitize-html": "^1.19.1",
npm update
2018-10-29 15:30:35 +01:00
"ua-parser-js": "^0.7.19",
move deps to sdk for stuff now in the sdk
2018-04-18 11:53:17 +02:00
"url": "^0.11.0"
Basic structure of a react SDK and start of an implementation.
2015-06-09 18:40:42 +02:00
},
"devDependencies": {
experimental postcss
2017-01-10 12:06:09 +01:00
"autoprefixer": "^6.6.0",
upgrade karma & babel to latest
2018-09-26 03:27:22 +02:00
"babel-cli": "^6.26.0",
Update a bunch of deps To try & get deps without vulns in them. Exceptions are: * electron builder: which is nontrivial to update * webpack-dev-server: probably needs newer webpack * moderizr: no new version released yet
2018-09-26 13:33:53 +02:00
"babel-core": "^6.26.3",
Revert "Revert "Run lint on travis builds and use modern node versions""
2018-11-22 19:25:55 +01:00
"babel-eslint": "^8.1.1",
find versions of webpack, webpack-cli, and karma-webpack which work together atm
2018-09-26 02:18:53 +02:00
"babel-loader": "^7.1.5",
Add plugin that makes babel 6 not break everything
2016-10-17 16:37:31 +02:00
"babel-plugin-add-module-exports": "^0.2.1",
add new babel plugins to deps
2019-04-30 13:48:18 +02:00
"babel-plugin-syntax-dynamic-import": "^6.18.0",
Transform `async` functions to bluebird promises It turns out that the assertion made in https://github.com/vector-im/riot-web/pull/4565 about `async` functions returning bluebird promises was only correct when babel used an inline version of the `asyncToGenerator` helper; in react-sdk we are using `babel-transform-runtime` which means that we use a separate `babel-runtime/helpers/asyncToGenerator`, which returns a native (or core-js) Promise. This meant that we were still in the situation where some methods returned native Promises, and some bluebird ones, which is exactly the situation I wanted to resolve by switching to bluebird in the first place: in short, unless/until we get rid of all code which assumes Promises have a `done` method etc, we need to make sure that everything returns a bluebird promise. (Aside: there was debate over whether in the long term we should be trying to wean ourselves off bluebird promises by assuming all promises are native. The conclusion was that the complexity hit involved in doing so outweighed any benefit of a potential future migration away from bluebird).
2017-07-13 18:34:47 +02:00
"babel-plugin-transform-async-to-bluebird": "^1.1.1",
add new babel plugins to deps
2019-04-30 13:48:18 +02:00
"babel-plugin-transform-builtin-extend": "^1.1.2",
upgrade karma & babel to latest
2018-09-26 03:27:22 +02:00
"babel-plugin-transform-class-properties": "^6.24.1",
"babel-plugin-transform-object-rest-spread": "^6.26.0",
"babel-plugin-transform-runtime": "^6.23.0",
"babel-preset-es2015": "^6.24.1",
"babel-preset-es2016": "^6.24.1",
"babel-preset-es2017": "^6.24.1",
"babel-preset-react": "^6.24.1",
"babel-preset-stage-2": "^6.24.1",
Update chokidar to transitively get newer fsevents Signed-off-by: J. Ryan Stinnett <jryans@gmail.com>
2018-10-25 23:04:25 +02:00
"chokidar": "^2.0.4",
Reduce the number of terminals required to build riot-web to 1 A step towards a real solution for https://github.com/vector-im/riot-web/issues/7305 This approach makes use of `npm link` to remove the use of symlinks in the build process. The build process has also been altered to invoke the build process of each underlying SDK (react, js). This means that one can now `npm link` and `npm start` and have a working environment. At the same time, parallelshell was dropped due to lack of maintenance from the maintainer.
2018-09-18 01:46:13 +02:00
"concurrently": "^4.0.1",
Various fixes and improvements to emojification. - Use locally hosted emoji - Emojify SenderProfile and m.emote - Fix emoji spacing
2016-08-09 18:14:09 +02:00
"cpx": "^1.3.2",
Add cross-env into the mix this way `npm run build` will work on Windows too :D Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-04-21 18:16:53 +02:00
"cross-env": "^4.0.0",
Process images with Webpack This adds a `file-loader` rule to the Webpack build so that any requests for image resource will be output into the app's output directory, but with an extra content has appended so that we can safely use a long cache lifetime. The CSS and SCSS rules are also changed to use `css-loader` so that any `url` inside is automatically processed by the new image rule above.
2019-01-01 00:22:47 +01:00
"css-loader": "^2.1.0",
Upgrade electron-builder, electron-builder-squirrel-windows to latest
2019-07-03 17:06:12 +02:00
"electron-builder": "^20.44.4",
"electron-builder-squirrel-windows": "^21.0.6",
Update a bunch of deps To try & get deps without vulns in them. Exceptions are: * electron builder: which is nontrivial to update * webpack-dev-server: probably needs newer webpack * moderizr: no new version released yet
2018-09-26 13:33:53 +02:00
"electron-devtools-installer": "^2.2.4",
npm update
2018-10-29 15:30:35 +01:00
"eslint": "^5.8.0",
Also need eslint-config-google
2017-01-24 14:07:34 +01:00
"eslint-config-google": "^0.7.1",
upgrade karma & babel to latest
2018-09-26 03:27:22 +02:00
"eslint-plugin-babel": "^4.1.2",
Actually update package.json
2018-09-28 12:02:14 +02:00
"eslint-plugin-flowtype": "^2.50.3",
"eslint-plugin-react": "^7.11.1",
Run some tests under karma Including a regression test for https://github.com/vector-im/vector-web/issues/1314
2016-04-13 11:15:04 +02:00
"expect": "^1.16.0",
Process images with Webpack This adds a `file-loader` rule to the Webpack build so that any requests for image resource will be output into the app's output directory, but with an extra content has appended so that we can safely use a long cache lifetime. The CSS and SCSS rules are also changed to use `css-loader` so that any `url` inside is automatically processed by the new image rule above.
2019-01-01 00:22:47 +01:00
"file-loader": "^3.0.1",
Exclude olm from the webpack Olm takes *ages* to webpack, and it doesn't compress well. So, serve it as a separate asset to the browser.
2016-08-02 13:42:06 +02:00
"fs-extra": "^0.30.0",
Update Webpack to version 4
2018-04-27 11:32:59 +02:00
"html-webpack-plugin": "^3.2.0",
Add config file for default hs/is urls
2015-10-02 12:48:52 +02:00
"json-loader": "^0.5.3",
Nudge karma to 3.1.2 This includes a fix for detecting the version of Chrome used to run tests.
2019-02-28 14:51:21 +01:00
"karma": "^3.1.2",
Set up BuildKite for Chrome
2019-03-14 02:46:52 +01:00
"karma-chrome-launcher": "^2.2.0",
upgrade karma & babel to latest
2018-09-26 03:27:22 +02:00
"karma-cli": "^1.0.1",
Enable fancy karma reporters cargo-cult luke's stuff from react-sdk
2017-08-08 20:05:58 +02:00
"karma-logcapture-reporter": "0.0.1",
upgrade karma & babel to latest
2018-09-26 03:27:22 +02:00
"karma-mocha": "^1.3.0",
Enable karma-sourcemap-loader This turns (some) stacktraces back into something useful, so that unpicking test failures is vaguely tractable
2017-08-08 20:04:25 +02:00
"karma-sourcemap-loader": "^0.3.7",
Enable fancy karma reporters cargo-cult luke's stuff from react-sdk
2017-08-08 20:05:58 +02:00
"karma-spec-reporter": "0.0.31",
Update a bunch of deps To try & get deps without vulns in them. Exceptions are: * electron builder: which is nontrivial to update * webpack-dev-server: probably needs newer webpack * moderizr: no new version released yet
2018-09-26 13:33:53 +02:00
"karma-summary-reporter": "^1.5.1",
pin karma-webpack to 4.0.0-beta.0 to fix perf regression so karma-webpack 3.0.5 is 4x slower than 4.0.0-beta.0 for webpacking for unknown reasons. However, 4.0.0-rc.1 and 4.0.0-rc.2 fail with a different error. So: pinned for now
2018-09-26 04:12:08 +02:00
"karma-webpack": "4.0.0-beta.0",
add content hash to individual language files
2019-02-18 16:11:41 +01:00
"loader-utils": "^1.2.3",
Update matrix-mock-request
2019-03-27 16:09:34 +01:00
"matrix-mock-request": "^1.2.3",
loading tests: wait for login component Rather than a fixed delay, use matrix-react-test-utils to wait for the login component to appear. Hopefully this will deflakify some tests.
2017-07-13 01:18:49 +02:00
"matrix-react-test-utils": "^0.2.0",
Use a custom script to copy resources (#2893) All of those cpx invocations were getting unwieldy, and I suspect the exotic quoting needed to run them under parallelshell was breaking things on windows. Replace the unwieldy cpx invocations with an unwieldy custom script.
2017-01-06 11:43:13 +01:00
"minimist": "^1.2.0",
Don't include two copies of the CSS in the tarball Aggregate our CSS into build/components.css instead of vector/components.css, so that it isn't included in the tarball.
2016-10-26 14:32:26 +02:00
"mkdirp": "^0.5.1",
Update a bunch of deps To try & get deps without vulns in them. Exceptions are: * electron builder: which is nontrivial to update * webpack-dev-server: probably needs newer webpack * moderizr: no new version released yet
2018-09-26 13:33:53 +02:00
"mocha": "^5.2.0",
experimental postcss
2017-01-10 12:06:09 +01:00
"postcss-extend": "^1.0.5",
Update Webpack to version 4
2018-04-27 11:32:59 +02:00
"postcss-import": "^11.1.0",
find versions of webpack, webpack-cli, and karma-webpack which work together atm
2018-09-26 02:18:53 +02:00
"postcss-loader": "^2.1.6",
Update Webpack to version 4
2018-04-27 11:32:59 +02:00
"postcss-mixins": "^6.2.0",
"postcss-nested": "^3.0.0",
find versions of webpack, webpack-cli, and karma-webpack which work together atm
2018-09-26 02:18:53 +02:00
"postcss-scss": "^1.0.6",
Update Webpack to version 4
2018-04-27 11:32:59 +02:00
"postcss-simple-vars": "^4.1.0",
experimental postcss
2017-01-10 12:06:09 +01:00
"postcss-strip-inline-comments": "^0.1.5",
Bump to react 15.4 Add dependencies on react 15.4. Some of the things we pull in from matrix-react-sdk won't work properly against 15.2 / 15.0.
2016-11-17 11:34:12 +01:00
"react-addons-perf": "^15.4.0",
Bump react to 15.6 to fix build problems matrix-react-test-tools requires react 15.6 or later, so make sure we require it in riot-web too.
2017-07-14 15:45:44 +02:00
"react-addons-test-utils": "^15.6.0",
Remove controllers that all come from react-sdk
2015-09-22 18:20:22 +02:00
"rimraf": "^2.4.3",
Actually update package.json
2018-09-28 12:02:14 +02:00
"source-map-loader": "^0.2.4",
npm update
2018-10-29 15:30:35 +01:00
"webpack": "^4.23.1",
update deps
2018-10-16 12:12:13 +02:00
"webpack-cli": "^3.1.2",
Update webpack-dev-server
2019-03-13 16:07:50 +01:00
"webpack-dev-server": "^3.1.11"
package.json: add olm as optionalDependency Add olm as an optionalDependency to vector, so that the webpack config can find it and include it in the bundle.
2016-06-20 16:10:19 +02:00
},
Electron support From https://github.com/vector-im/vector-web/pull/2511 but with just the actual electron changes
2016-11-02 19:49:28 +01:00
"build": {
"appId": "im.riot.app",
Upgrade to Electron 5 The APIs related to custom protocols went through some changes for Electron 5.x, so adjusts Riot's usages to match. I have scanned the Electron 5.x release notes, and I can't see anything else that requires immediate changes. Things appear to be working well after the upgrade. Fixes https://github.com/vector-im/riot-web/issues/10296 Fixes https://github.com/vector-im/riot-web/issues/9562
2019-07-22 15:32:50 +02:00
"electronVersion": "5.0.7",
Electron support From https://github.com/vector-im/vector-web/pull/2511 but with just the actual electron changes
2016-11-02 19:49:28 +01:00
"files": [
Proper two package.json format, release.sh bumps 2nd json ver too Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-05 17:54:55 +02:00
"node_modules/**",
Move default Electron icons outside asar Electron doesn't seem to want to load icons from within `asar`s, so this changes the default icons (used for window and tray) so that they are just regular files on disk and updates the reference to match. Part of https://github.com/vector-im/riot-web/issues/9897
2019-06-18 17:12:38 +02:00
"src/**"
Proper two package.json format, release.sh bumps 2nd json ver too Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-05 17:54:55 +02:00
],
"extraResources": [
Upgrade electron-builder, electron-builder-squirrel-windows to latest
2019-07-03 17:06:12 +02:00
{
"from": "electron_app/img",
"to": "img"
},
Add tool to migrate logins between origins App checks at startup for an existing session, if there isn't one, it will start the tool to check for a login in the file:// origin. If there is one, it will copy the login over to the vector://vector origin. In principle this could also be used to migrate logins between other origins on the web if this were ever required. This includes a minified copy of the browserified js-sdk with a getAllEndToEndSessions() function added to the crypto store (https://github.com/matrix-org/matrix-js-sdk/pull/812). This is not great, but for a short-lived tool this seems better than introducing more entry points into webpack only used for the electron app.
2018-12-21 20:14:25 +01:00
"webapp/**/*",
"origin_migrator/**/*"
Slight grab-bag of fixes for electron on Windows * Implement the squirrel install / uninstall hooks (so we have a start menu entry / desktop shortcut) * Wait longer before checking for update * Set the window icon * Add a 'file' menu * Bump electron-builder * Add the icon url for the control panel entry
2016-11-07 12:41:41 +01:00
],
Switch to new auto-update & add linux build * Remove squirrel hooks (the installing & uninstalling is now done by the, er, installer) * Switch to electron-auto-update * Shorten initial update delay because we no longer need to wait for squirrel to release a lock file * Change update URLs because windows is now one installer for both 32 & 64 bit. * Update electron-builder to 10 where NSIS is now the default target for Windows. * Add linux to the target list, building a deb. * Remove sqirrel-specific installation spinner * Remove redundant !**/* from files
2016-12-01 12:35:26 +01:00
"linux": {
"target": "deb",
Add `Chat` to Linux app categories most dists inc Arch have Chat and IRCClient, though the latter isn't exactly correct so missing it
2017-05-25 14:22:01 +02:00
"category": "Network;InstantMessaging;Chat",
Add StartupWMClass so GNOME doesn't get confused by the hidden windows
2017-01-19 17:21:43 +01:00
"maintainer": "support@riot.im",
"desktop": {
rename WMClass as riot rather than confusing riot-web
2017-06-03 19:43:06 +02:00
"StartupWMClass": "riot"
Add StartupWMClass so GNOME doesn't get confused by the hidden windows
2017-01-19 17:21:43 +01:00
}
Switch back to Squirrel installer which it turns out is by far the lesser of two evils. * Auto-update works with a proxy * The update process is reasonably atomic & faster, rather than running the uninstaller then the installer, leaving you with a broken install if you shut down your machine at the wrong time * Gets the update URL the same way as on mac, rather than baking it into the app at build time from package.json. We don't want it in package.json because only our builds want our update URL.
2016-12-05 15:08:27 +01:00
},
Update to latest electron builder Tested auto update on both windows (ia32) and mac, seems to work!
2018-10-15 19:13:47 +02:00
"mac": {
"category": "public.app-category.social-networking"
},
Switch back to Squirrel installer which it turns out is by far the lesser of two evils. * Auto-update works with a proxy * The update process is reasonably atomic & faster, rather than running the uninstaller then the installer, leaving you with a broken install if you shut down your machine at the wrong time * Gets the update URL the same way as on mac, rather than baking it into the app at build time from package.json. We don't want it in package.json because only our builds want our update URL.
2016-12-05 15:08:27 +01:00
"win": {
Update to latest electron builder Tested auto update on both windows (ia32) and mac, seems to work!
2018-10-15 19:13:47 +02:00
"target": {
"target": "squirrel"
}
Fix packaged functionality Improve dependency management for Electron main process deps Dependencies in /electron/package.json will be installed through a script in /package.json and will be bundled via electron-builder Does not affect standard webapp whatsoever Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-04-13 14:39:15 +02:00
},
"directories": {
npm is "smart" enough to try and install our electron wrapper as a module instead of the actual electron package. With no way to ignore directories. I'd like to think of this as temporary, until I get to rip apart riot-web and riot-electron Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-10 14:36:27 +02:00
"buildResources": "electron_app/build",
"output": "electron_app/dist",
"app": "electron_app"
Slight grab-bag of fixes for electron on Windows * Implement the squirrel install / uninstall hooks (so we have a start menu entry / desktop shortcut) * Wait longer before checking for update * Set the window icon * Add a 'file' menu * Bump electron-builder * Add the icon url for the control panel entry
2016-11-07 12:41:41 +01:00
}
Basic structure of a react SDK and start of an implementation.
2015-06-09 18:40:42 +02:00
}
}