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

184 lines
6.7 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",
v0.16.4
2018-09-10 12:43:23 +02:00
"version": "0.16.4",
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",
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",
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
"build:compile": "npm run reskindex && babel --source-maps -d lib src",
Make webpack exit non-zero on error Pass `--bail` to webpack, so that if we can't find a module, we bail out rather than deploy a broken version to /develop. https://github.com/webpack/webpack/issues/708 is somewhat relevant.
2017-08-08 10:42:38 +02:00
"build:bundle": "cross-env NODE_ENV=production webpack -p --progress --bail",
"build:bundle:dev": "webpack --optimize-occurence-order --progress --bail",
explicitly call install:electron in case electron-builder is silly (which has hit me once) Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-30 13:35:57 +02:00
"build:electron": "npm run clean && npm run build && npm run install:electron && build -wml --ia32 --x64",
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
"build:react-sdk": "node scripts/build-watch-sdk.js build react",
"build:js-sdk": "node scripts//build-watch-sdk.js build js",
"build": "npm run build:js-sdk && npm run build:react-sdk && npm run reskindex && npm run build:res && npm run build:bundle",
"build:dev": "npm run build:js-sdk && npm run build:react-sdk && npm run reskindex && npm run build:res && npm run 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",
Only install electron deps when we're bundling/running electron Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-05 18:01:32 +02:00
"install:electron": "install-app-deps",
don't hook on postinstall, current dev cycle uses (abuses) npm i to build so no point making it take longer than it has to for the devs only testing webapp build:electron - hook npm run install:electron install:electron - run npm i for the electron deps electron - start the app locally for testing add to README Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-04-23 23:50:58 +02:00
"electron": "npm run 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",
Add --output-chunk-file too
2017-01-25 12:28:59 +01:00
"start:js": "webpack-dev-server --output-filename=bundles/_dev_/[name].js --output-chunk-file=bundles/_dev_/[name].js -w --progress",
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
"start:js:prod": "cross-env NODE_ENV=production webpack-dev-server -w --progress",
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
"start:js-sdk": "node scripts//build-watch-sdk.js watch js",
"start:js-sdk:prod": "cross-env NODE_ENV=production node scripts//build-watch-sdk.js watch js",
"start:react-sdk": "node scripts//build-watch-sdk.js watch react",
"start:react-sdk:prod": "cross-env NODE_ENV=production node scripts//build-watch-sdk.js watch react",
"start": "concurrently --kill-others -n js-sdk,react-sdk,reskindex,res,js \"npm run start:js-sdk\" \"npm run start:react-sdk\" \"npm run reskindex:watch\" \"npm run start:res\" \"npm run start:js\"",
"start:prod": "concurrently --kill-others -n js-sdk,react-sdk,reskindex,res,js \"npm run start:js-sdk:prod\" \"npm run start:react-sdk:prod\" \"npm run reskindex:watch\" \"npm run start:res\" \"npm run 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",
Clean on prepublish (#5097) Otherwise you can make broken releases on case insensitive file systems
2017-09-21 19:06:41 +02:00
"prepublish": "npm run clean && npm run build:compile",
Enable colours for karma test output I don't really know why we disable colours here.
2017-07-13 01:18:10 +02:00
"test": "karma start --single-run=true --autoWatch=false --browsers ChromeHeadless",
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": {
Remove transform-runtime We use instance methods (or at least, draft.js does) so we need babel-polyfill instead.
2016-10-13 11:57:10 +02:00
"babel-polyfill": "^6.5.0",
Upgrade to babel6 and enable some presets.
2016-10-02 13:58:24 +02:00
"babel-runtime": "^6.11.6",
replace imports of `q` with bluebird update `package.json` ``` find src test -name '*.js' | xargs perl -i -pe 'if (/require\(.[qQ].\)/) { $_ = "import Promise from '\''bluebird'\'';\n"; }' find src test -name '*.js' | xargs perl -i -pe 'if (/import [qQ] /) { $_ = "import Promise from '\''bluebird'\'';\n"; }' ```
2017-07-13 01:48:31 +02:00
"bluebird": "^3.5.0",
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",
Run the CSS through webpack so we can pull in CSS files from modules with require rather than symlinking into the node_module directory which is breaking people on different npm versions.
2015-12-01 19:05:43 +01:00
"extract-text-webpack-plugin": "^0.9.1",
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",
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
"gemini-scrollbar": "matrix-org/gemini-scrollbar#b302279",
"gfm.css": "^1.1.1",
"highlight.js": "^9.0.0",
Released js-sdk & react-sdk
2018-09-10 12:41:45 +02:00
"matrix-js-sdk": "0.11.0",
"matrix-react-sdk": "0.13.4",
upgrade to react 0.14
2015-11-10 00:13:46 +01:00
"modernizr": "^3.1.0",
install and use prop-types over React.PropTypes Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-09-13 15:23:35 +02:00
"prop-types": "^15.5.10",
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",
Unpin sanitize-html 1.18.4 is now out which makes it work with webpack again
2018-08-02 17:22:07 +02:00
"sanitize-html": "^1.18.4",
Make up a device display name Pass a default device name into react-sdk
2016-08-12 12:01:01 +02:00
"ua-parser-js": "^0.7.10",
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 to babel6 and enable some presets.
2016-10-02 13:58:24 +02:00
"babel-cli": "^6.5.2",
"babel-core": "^6.14.0",
"babel-eslint": "^6.1.0",
"babel-loader": "^6.2.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",
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",
Replace stage & es2017 with specific plugins Also sort out regenerator runtime as it turns out importing babel-polyfill in your code is insufficient if using webpack because it's imported too late, so use both that and regenerator-runtime. Sigh.
2016-10-14 19:03:22 +02:00
"babel-plugin-transform-class-properties": "^6.16.0",
"babel-plugin-transform-object-rest-spread": "^6.16.0",
Upgrade to babel6 and enable some presets.
2016-10-02 13:58:24 +02:00
"babel-plugin-transform-runtime": "^6.15.0",
"babel-preset-es2015": "^6.16.0",
"babel-preset-es2016": "^6.16.0",
"babel-preset-es2017": "^6.16.0",
"babel-preset-react": "^6.16.0",
Reminder to restore links + stage2, not stage 0
2016-10-12 19:08:52 +02:00
"babel-preset-stage-2": "^6.17.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
"chokidar": "^1.6.1",
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",
Run the CSS through webpack so we can pull in CSS files from modules with require rather than symlinking into the node_module directory which is breaking people on different npm versions.
2015-12-01 19:05:43 +01:00
"css-raw-loader": "^0.1.1",
Hopefully fix Windows shortcuts * Revert https://github.com/vector-im/riot-web/commit/79d164309f7926cb1c24008e464a516d7a872325 as it seems to break shortcuts altogether * Update electron-builder (and add the squirrel windows package that the newer version now requires: it's been split out). This uses a newer version of squirrel which has some fixes for shortcuts. I'm unsure exactly what was going wrong originally in https://github.com/vector-im/riot-web/issues/2775 but #79d1643 seems to break shortcut creation as far as I can see.
2017-01-11 17:27:40 +01:00
"electron-builder": "^11.2.4",
"electron-builder-squirrel-windows": "^11.2.1",
provide react devtools in electron dev builds Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-06-04 16:30:44 +02:00
"electron-devtools-installer": "^2.2.0",
bump emojione
2017-04-01 02:28:44 +02:00
"emojione": "^2.2.7",
Add eslint config An early start that gets some linting in place.
2017-01-23 15:22:54 +01:00
"eslint": "^3.14.0",
Also need eslint-config-google
2017-01-24 14:07:34 +01:00
"eslint-config-google": "^0.7.1",
Add babel eslint plugin As our linter has been failing because it needs it
2017-05-26 23:59:40 +02:00
"eslint-plugin-babel": "^4.1.1",
Add eslint config An early start that gets some linting in place.
2017-01-23 15:22:54 +01:00
"eslint-plugin-flowtype": "^2.30.0",
bump version to prevent eslint errors got bumped in react-sdk, missed here Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-10-17 15:44:41 +02:00
"eslint-plugin-react": "^7.4.0",
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",
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",
Put a cachebuster in the names of CSS and JS files This means that clients can do better caching of assets, as it will mean we are no longer reliant on etags to ensure that clients get a fresh version. We inhibit the cachebuster for `npm start`, so that we don't get millions of copies of the bundles on dev boxes.
2016-10-25 18:07:43 +02:00
"html-webpack-plugin": "^2.24.0",
Add config file for default hs/is urls
2015-10-02 12:48:52 +02:00
"json-loader": "^0.5.3",
Enable fancy karma reporters cargo-cult luke's stuff from react-sdk
2017-08-08 20:05:58 +02:00
"karma": "^1.7.0",
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
"karma-chrome-launcher": "^0.2.3",
"karma-cli": "^0.1.2",
"karma-junit-reporter": "^0.4.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",
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
"karma-mocha": "^0.2.2",
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",
"karma-summary-reporter": "^1.3.3",
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
"karma-webpack": "^1.7.0",
Deflake the joining test Just give the client longer to get started (it seems to be taking a long time to get started talking to indexeddb)
2017-07-14 17:14:42 +02:00
"matrix-mock-request": "^1.2.0",
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",
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
"mocha": "^2.4.5",
experimental postcss
2017-01-10 12:06:09 +01:00
"postcss-extend": "^1.0.5",
"postcss-import": "^9.0.0",
Use the postcss-webpack-loader Use postcss-webpack-loader instead of webpack-cli to process the scss. Doing so mostly means that we avoid the problem that webpack-dev-server fails to start if we haven't already built the CSS. (It also simplifies package.json somewhat, which is no bad thing)
2017-01-19 03:48:17 +01:00
"postcss-loader": "^1.2.2",
experimental postcss
2017-01-10 12:06:09 +01:00
"postcss-mixins": "^5.4.1",
"postcss-nested": "^1.0.0",
"postcss-scss": "^0.4.0",
"postcss-simple-vars": "^3.0.0",
"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",
Bump source-map-loader version to avoid bug /w inline base64 maps
2018-04-09 14:50:43 +02:00
"source-map-loader": "^0.2.3",
Use webpack-dev-server instead of http-server Advantages: * blocks while a rebuild is in progress so you're less likely to reload the old version * serves from memory rather than disk, so we no longer need to turn off the cachebuster to avoid filling the disk with bundles. Empirically, seems to last a plausible amount of time without OOMing; there's no real reason to believe it would use any more memory than webpack itself. * That in turn means we no longer need the hack to stop chrome caching old sourcemaps (because the sourcemap now has a cachebuster in its name). * one fewer process for parallelshell to (fail to) manage. * in future, we could consider the fancy hot-reload functionality.
2016-11-03 15:58:30 +01:00
"webpack": "^1.12.14",
"webpack-dev-server": "^1.16.2"
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
},
"optionalDependencies": {
Bump olm version Looks like this is causing pickle errors on packaged builds.
2017-02-03 14:51:02 +01:00
"olm": "https://matrix.org/packages/npm/olm/olm-2.2.1.tgz"
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",
"category": "Network",
electron 2.0.8
2018-08-30 12:38:20 +02:00
"electronVersion": "2.0.8",
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
"//asar=false": "https://github.com/electron-userland/electron-builder/issues/675",
"asar": false,
"dereference": true,
Build to the 'webapp' directory instead People may have config files in vector/ so it would be nonideal if we started overwriting them / blowing them away.
2016-11-08 16:46:21 +01:00
"//files": "We bundle everything, so we only need to include webapp/",
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/**",
"src/**",
"img/**"
],
"extraResources": [
"webapp/**/*"
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
},
"win": {
v0.9.1-rc.1
2016-12-05 19:02:03 +01:00
"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
}
}