oxen-io/session-desktop
1
0
Fork 0
mirror of https://github.com/oxen-io/session-desktop.git synced 2023-12-14 02:12:57 +01:00
Code Issues Projects Releases Wiki Activity
session-desktop/package.json

275 lines
9.3 KiB
JSON
Raw Normal View History

Grunt preen and concat Set up grunt with tasks for: * preen - deletes unused files from bower_components, configured in bower.json * concat - concatenates preened bower components, configured automagically from the preen config It's worth noting that this setup assumes the order of files within a package doesn't matter. This is usually true since we often include only one file from the package.
2014-10-30 02:32:29 +01:00
{
Update project/repo names in package.json // FREEBIE
2016-01-01 23:23:44 +01:00
"name": "signal-desktop",
Add productName to package.json This defines the display name of the packaged app. It can contain spaces. // FREEBIE
2017-03-31 01:40:09 +02:00
"productName": "Signal",
Populate required fields in package.json // FREEBIE
2017-03-08 01:55:24 +01:00
"description": "Private messaging from your desktop",
Big update to new signal branding (#2018)
2018-01-30 23:22:51 +01:00
"repository": "https://github.com/signalapp/Signal-Desktop.git",
v1.23.2-beta.1
2019-03-29 02:42:23 +01:00
"version": "1.23.2-beta.1",
Populate required fields in package.json // FREEBIE
2017-03-08 01:55:24 +01:00
"license": "GPL-3.0",
"author": {
"name": "Open Whisper Systems",
Big update to new signal branding (#2018)
2018-01-30 23:22:51 +01:00
"email": "support@signal.org"
Populate required fields in package.json // FREEBIE
2017-03-08 01:55:24 +01:00
},
Hello Electron In package.json, define our main entry point for electron, and add a node script to start it up. Add main.js from Electron/electron-quick-start with two modifications. 1. Load background.html instead of index.html 2. Disable node integration in the renderer At this point we can load the background page in a window with `npm start`, though it currently breaks on missing chrome app APIs. // FREEBIE
2017-03-02 23:04:38 +01:00
"main": "main.js",
Run tests on Sauce Labs * Issue #57
2014-11-23 04:36:52 +01:00
"scripts": {
Move logging to disk via bunyan - Logging is available in main process as well as renderer process, and entries all go to one set of rotating files. Log entries in the renderer process go to DevTools as well as the console. Entries from the main process only show up in the console. - We save three days of logs, one day per file in %userData%/logs - The 'debug' object store is deleted in a new database migration - Timestamps and level included in the new log we generate for publish as well as the devtools - The bunyan API is exposed via windows.log (providing the ability to log at different levels, and save objects instead of just text), so we can move our code to it over time. FREEBIE
2017-09-26 00:00:19 +02:00
"postinstall": "electron-builder install-app-deps && rimraf node_modules/dtrace-provider",
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
"start": "electron .",
Remove unused asarl package.json script, rearrange a little
2018-05-01 18:49:22 +02:00
"grunt": "grunt",
Generate icons with electron-icon-maker Either icon-gen or local scaling of images was producing a corrupted and glitchy .icns file. With this module, we need only provide a 1024px image and it handles the scaling and generation of all other icon assets. // FREEBIE
2017-04-21 23:31:58 +02:00
"icon-gen": "electron-icon-maker --input=images/icon_1024.png --output=./build",
Run all build steps in CI
2018-05-07 21:53:20 +02:00
"generate": "yarn icon-gen && yarn grunt",
Upgrade to Electron 1.8.2 / Node.js 8.2.1 (#2066) * Upgrade to Electron 1.8.2 / Node.js 8.2.1 * Update CI Node.js versions * Make `engines` top-level property This was accidentally included under `build` which is disallowed by `electron-builder`. * Refactor notification updates Allows easier debugging through variable inspection. * Use `appId` for Application User Model ID Recommended in: https://github.com/electron/electron/issues/10864#issuecomment-346229090 * Update `spectron` to 3.8.0 * Bump `electron-builder` based dependencies * Use `config.extraMetadata` instead of `em` Prevents `Unknown argument: em` error. See: https://github.com/electron-userland/electron-builder/issues/2615 * Revert AUMID to be based on `packageJson.name` In our build artifact `packageJson.build.appId` causes an NPE.
2018-03-02 20:43:03 +01:00
"build": "build --config.extraMetadata.environment=$SIGNAL_ENV",
package.json: Remove all but the scripts needed for modern build
2018-05-01 07:36:21 +02:00
"build-release": "SIGNAL_ENV=production npm run build -- --config.directories.output=release",
Compile all protocol buffers
2018-05-08 01:08:43 +02:00
"build-module-protobuf": "pbjs --target static-module --wrap commonjs --out ts/protobuf/compiled.js protos/*.proto && pbts --out ts/protobuf/compiled.d.ts ts/protobuf/compiled.js",
"clean-module-protobuf": "rm -f ts/protobuf/compiled.d.ts ts/protobuf/compiled.js",
Revert "Use protocol buffer module for `libtextsecure`" This does not work with `ArrayBuffer` out of the box and will need to be investigated and tested more before switching. Some APIs also seemed to have changed: - Before (OOP): `new textsecure.protobuf.WebSocketMessage(…).encode();` - After (functional): ``` textsecure.protobuf.WebSocketMessage.encode( new textsecure.protobuf.WebSocketMessage(…) ); ``` This reverts commit d758119d9de4f99742ea941e86180b1d600c2f22.
2018-05-08 01:12:53 +02:00
"build-protobuf": "yarn build-module-protobuf",
"clean-protobuf": "yarn clean-module-protobuf",
New design for import/install, 'light' import (#2053) - A new design for the import flow. It features: - Icons at the top of every screen - Gray background, blue buttons, thinner text - Simpler copy - A new design for the install flow. It features: - Immediate entry into the QR code screen - Animated dots to show that we're loading the QR code from the server - Fewer screens: 1) QR 2) device name 3) sync-in-progress - When not set up, the app opens directly into the install screen, which has been streamlined. The `--import` command-line argument will cause the app to open directly into the import flow. - Support for two different flavors of builds - the normal build will open into the standard registration flow, and the import flavor will be exactly the same except during setup it will open directly into the import flow. - A new design for the (dev-only) standalone registration view - When these install sequences are active, the OS File menu has entries to allow you to switch the method of setup you'd like to use. These go away as soon as the first step is taken in any of these flows. - The device name (chosen on initial setup) is now shown in the settings panel - At the end of a light import, we hand off to the normal device link screen, starting at the QR code. On a full import, we remove the sensitive encryption information in the export to prevent conflicts on multiple imports. - `Whisper.Backup.exportToDirectory()` takes an options object so you can tell it to do a light export. - `Whisper.Backup.importFromDirectory()` takes an options object so you can force it to load only the light components found on disk. It also returns an object so you can tell whether a given import was a full import or light import. - On start of import, we build a list of all the ids present in the messages, conversations, and groups stores in IndexedDB. This can take some time if a lot of data is in the database already, but it makes the subsequent deduplicated import very fast. - Disappearing messages are now excluded when exporting - Remove some TODOs in the tests
2018-02-22 19:40:32 +01:00
"prepare-beta-build": "node prepare_beta_build.js",
"prepare-import-build": "node prepare_import_build.js",
package.json: Remove all but the scripts needed for modern build
2018-05-01 07:36:21 +02:00
"publish-to-apt": "NAME=$npm_package_name VERSION=$npm_package_version ./aptly.sh",
Simplify testing and linting Separate linting from testing as follows: - `yarn jscs`: Run JSCS. - `yarn jshint`: Run JSHint. - `yarn lint`: Run all linters, i.e. ESLint, TSLint, JSHint, and JSHint. - `yarn test-node`: Run Mocha tests in Node.js environment. - `yarn test-electron`: Run tests in Electron environment via Grunt. - `yarn test`: Run all tests. CI - Align Travis and AppVeyor scripts as much as possible. - Run linting before tests to fail fast. - Run Node.js (headless and fast) tests first. - Run Electron tests last (Travis seems to require custom setup in `travis.sh`).
2018-04-10 23:47:25 +02:00
"test": "yarn test-node && yarn test-electron",
Organize npm scripts Combine `yarn grunt jshint` and `yarn grunt jscs` into `yarn grunt lint`.
2018-04-11 20:57:15 +02:00
"test-electron": "yarn grunt test",
Rename `ts/test` to `ts/styleguide`
2018-04-11 22:31:35 +02:00
"test-node": "mocha --recursive test/app test/modules ts/test",
"test-node-coverage": "nyc --reporter=lcov --reporter=text mocha --recursive test/app test/modules ts/test",
Organize npm scripts Combine `yarn grunt jshint` and `yarn grunt jscs` into `yarn grunt lint`.
2018-04-11 20:57:15 +02:00
"eslint": "eslint .",
Run `yarn lint-windows` without Prettier for AppVeyor We need to figure out how to run globs on Windows.
2018-05-01 00:13:30 +02:00
"lint": "yarn format --list-different && yarn lint-windows",
Remove jshint - move everything over to eslint Also removed all hints of previous linters
2018-07-07 02:48:14 +02:00
"lint-windows": "yarn eslint && yarn tslint",
Custom linter to check code quality (#2753)
2018-09-21 00:24:52 +02:00
"lint-deps": "node ts/util/lint/linter.js",
Turn on all of Microsoft's recommend lint rules Biggest changes forced by this: alt tags for all images, resulting in new strings added to messages.json, and a new i18n paramter/prop added in a plot of places. Another change of note is that there are two new tslint.json files under ts/test and ts/styleguide to relax our rules a bit there. This required a change to our package.json script, as manually specifying the config file there made it ignore our tslint.json files in subdirectories
2018-05-22 21:31:43 +02:00
"tslint": "tslint --format stylish --project .",
Prettier: Format CSS, SCSS, and JSON
2018-05-04 22:04:06 +02:00
"format": "prettier --write \"*.{css,js,json,md,scss,ts,tsx}\" \"./**/*.{css,js,json,md,scss,ts,tsx}\"",
Introduce React/TypeScript/TSLint into app for new UI components npm run transpile Works on files under js/react/ Outputs files right next to the .tsx file This is part of our `grunt dev` task, as well as the default grunt task, which does everything else necessary to get a raw git checkout ready to run.
2018-03-26 20:44:45 +02:00
"transpile": "tsc",
yarn clean-transpile: ensure that it always gets everything
2019-04-03 02:46:30 +02:00
"clean-transpile": "rimraf ts/**/*.js && rimraf ts/*.js",
Full styleguide now available via `yarn styleguide` Due to a number of hacks, the style guide can be used to show Backbone views. This will allow a smooth path from the old way of doing things to the new.
2018-04-04 00:56:12 +02:00
"open-coverage": "open coverage/lcov-report/index.html",
"styleguide": "styleguidist server"
Clean logs on start - and eslint/mocha with code coverage (#1945) * Clean logs on startup; install server-side testing/linting * Add eslint config, make all of app/ conform to its demands * Add Node.js testing and linting to CI * Lock project to Node.js 7.9.0, used by Electron 1.7.10 * New eslint error: trailing commas in function argumensts Node 7.9.0 doesn't like trailing commas, but Electron does * Move electron to devDependency, tell eslint it's built-in
2018-01-08 22:19:25 +01:00
},
"dependencies": {
Update sqlcipher dependency to get win vc++ redistributable
2019-03-22 19:06:33 +01:00
"@journeyapps/sqlcipher": "https://github.com/scottnonnenberg-signal/node-sqlcipher.git#2e28733b61640556b0272a3bfc78b0357daf71e6",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"@sindresorhus/is": "0.8.0",
Render only visible conversations in left pane
2019-03-09 03:25:28 +01:00
"@types/react-virtualized": "9.18.12",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"backbone": "1.3.3",
"blob-util": "1.3.0",
"blueimp-canvas-to-blob": "3.14.0",
"blueimp-load-image": "2.18.0",
"bunyan": "1.8.12",
"classnames": "2.2.5",
"config": "1.28.1",
"electron-editor-context-menu": "1.1.1",
"electron-is-dev": "0.3.0",
Upgrade electron-builder and electron-updater
2019-03-22 20:24:07 +01:00
"electron-updater": "3.2.0",
Clean logs on start - and eslint/mocha with code coverage (#1945) * Clean logs on startup; install server-side testing/linting * Add eslint config, make all of app/ conform to its demands * Add Node.js testing and linting to CI * Lock project to Node.js 7.9.0, used by Electron 1.7.10 * New eslint error: trailing commas in function argumensts Node 7.9.0 doesn't like trailing commas, but Electron does * Move electron to devDependency, tell eslint it's built-in
2018-01-08 22:19:25 +01:00
"emoji-datasource": "4.0.0",
"emoji-datasource-apple": "4.0.0",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"emoji-js": "3.4.0",
Move all forks to @scottnonnenberg-signal account
2018-05-22 01:43:02 +02:00
"emoji-panel": "https://github.com/scottnonnenberg-signal/emoji-panel.git#v0.5.5",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"filesize": "3.6.1",
"firstline": "1.2.1",
"form-data": "2.3.2",
"fs-extra": "5.0.0",
"glob": "7.1.2",
"google-libphonenumber": "3.0.7",
"got": "8.2.0",
Link Previews
2019-01-16 04:03:56 +01:00
"he": "1.2.0",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"intl-tel-input": "12.1.15",
"jquery": "3.3.1",
"linkify-it": "2.0.3",
Update lodash to latest release
2018-11-27 03:09:50 +01:00
"lodash": "4.17.11",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"mkdirp": "0.5.1",
"moment": "2.21.0",
"mustache": "2.3.0",
Move all forks to @scottnonnenberg-signal account
2018-05-22 01:43:02 +02:00
"node-fetch": "https://github.com/scottnonnenberg-signal/node-fetch.git#3e5f51e08c647ee5f20c43b15cf2d352d61c36b4",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"node-gyp": "3.8.0",
"node-sass": "4.9.3",
"os-locale": "2.1.0",
"pify": "3.0.0",
Move left pane entirely to React
2019-01-14 22:49:58 +01:00
"protobufjs": "6.8.6",
Update proxy-agent to latest
2018-11-27 18:53:02 +01:00
"proxy-agent": "3.0.3",
Move left pane entirely to React
2019-01-14 22:49:58 +01:00
"react": "16.8.3",
Update react-contextmenu to avoid event handler issues un unload
2019-03-20 21:43:24 +01:00
"react-contextmenu": "2.11.0",
Move left pane entirely to React
2019-01-14 22:49:58 +01:00
"react-dom": "16.8.3",
"react-redux": "6.0.1",
"react-virtualized": "9.21.0",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"read-last-lines": "1.3.0",
Move left pane entirely to React
2019-01-14 22:49:58 +01:00
"redux": "4.0.1",
"redux-logger": "3.0.6",
"redux-promise-middleware": "6.1.0",
"reselect": "4.0.0",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"rimraf": "2.6.2",
"semver": "5.4.1",
Update spellchecker to reenable spellcheck on linux w/electron v4
2019-03-19 00:22:40 +01:00
"spellchecker": "3.5.1",
Updates to backup infrastructure
2018-12-13 22:41:42 +01:00
"tar": "4.4.8",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"testcheck": "1.0.0-rc.2",
"tmp": "0.0.33",
"to-arraybuffer": "1.0.1",
"underscore": "1.9.0",
"uuid": "3.3.2",
Update websocket dep; 1.0.25 was causing errors w/Electron3
2018-11-16 02:36:57 +01:00
"websocket": "1.0.28"
Clean logs on start - and eslint/mocha with code coverage (#1945) * Clean logs on startup; install server-side testing/linting * Add eslint config, make all of app/ conform to its demands * Add Node.js testing and linting to CI * Lock project to Node.js 7.9.0, used by Electron 1.7.10 * New eslint error: trailing commas in function argumensts Node 7.9.0 doesn't like trailing commas, but Electron does * Move electron to devDependency, tell eslint it's built-in
2018-01-08 22:19:25 +01:00
},
"devDependencies": {
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"@types/chai": "4.1.2",
"@types/classnames": "2.2.3",
"@types/filesize": "3.6.0",
"@types/google-libphonenumber": "7.4.14",
Move left pane entirely to React
2019-01-14 22:49:58 +01:00
"@types/jquery": "3.3.29",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"@types/linkify-it": "2.0.3",
"@types/lodash": "4.14.106",
"@types/mocha": "5.0.0",
"@types/qs": "6.5.1",
Move left pane entirely to React
2019-01-14 22:49:58 +01:00
"@types/react": "16.8.5",
"@types/react-dom": "16.8.2",
"@types/react-redux": "7.0.1",
"@types/redux-logger": "3.0.7",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"@types/semver": "5.5.0",
"@types/sinon": "4.3.1",
"arraybuffer-loader": "1.0.3",
"asar": "0.14.0",
"bower": "1.8.2",
"chai": "4.1.2",
Update to Electron v4.1.2 to fix permissions issue https://github.com/electron/electron/releases/tag/v4.1.2 Permissions issue: https://github.com/electron/electron/issues/17581
2019-03-28 21:34:53 +01:00
"electron": "4.1.2",
Upgrade electron-builder and electron-updater
2019-03-22 20:24:07 +01:00
"electron-builder": "20.33.1",
Dependency updates, fixes required for successful release (#1966) * A number of fixes required for successful build after upgrades - extract now takes an absolute directory only - something changed, so we now need to force NODE_ENV=production; we use electron-is-dev for this - electron-builder, electron-publisher-s3, and electron-updater are now updated to their latest available versions * Add direct dependency on extract-zip, since we use it directly * Load 'config' module after we've modified NODE_ENV * Downgrade electron-builder due to bug, downgrade icon-maker too The latest electron-builder came with a fix for one of our bugs as well as a new bug that blocks builds on Windows: https://github.com/electron-userland/electron-builder/issues/2462 There's no good reason to upgrade icon-maker. And a good reason to keep at the version on github: https://github.com/jaretburkett/electron-icon-maker/issues/7
2018-01-13 01:14:45 +01:00
"electron-icon-maker": "0.0.3",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"eslint": "4.14.0",
"eslint-config-airbnb-base": "12.1.0",
"eslint-config-prettier": "2.9.0",
"eslint-plugin-import": "2.8.0",
"eslint-plugin-mocha": "4.12.1",
"eslint-plugin-more": "0.3.1",
"extract-zip": "1.6.6",
"grunt": "1.0.1",
"grunt-cli": "1.2.0",
"grunt-contrib-concat": "1.0.1",
"grunt-contrib-copy": "1.0.0",
"grunt-contrib-watch": "1.0.0",
"grunt-exec": "3.0.0",
"grunt-gitinfo": "0.1.7",
"grunt-sass": "3.0.1",
"mocha": "4.1.0",
"mocha-testcheck": "1.0.0-rc.0",
"node-sass-import-once": "1.2.0",
"nyc": "11.4.1",
Add `prettier`
2018-04-13 17:23:38 +02:00
"prettier": "1.12.0",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"qs": "6.5.1",
"react-docgen-typescript": "1.2.6",
"react-styleguidist": "7.0.1",
"sinon": "4.4.2",
Enable CI and packaged builds with Electron v3 (#2939) * Update spectron to fix linux CI runs * Point test-release grunt task at release folder * Ensure that build folders of socks/smart-buffer are in build * AppVeyor: windows build output folder is now release * Travis: Force build output to release directory
2018-11-28 01:20:48 +01:00
"spectron": "5.0.0",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"ts-loader": "4.1.0",
Move left pane entirely to React
2019-01-14 22:49:58 +01:00
"tslint": "5.13.0",
"tslint-microsoft-contrib": "6.0.0",
"tslint-react": "3.6.0",
"typescript": "3.3.3333",
package.json: Lock all dependencies to specific versions
2018-11-16 02:08:35 +01:00
"webpack": "4.4.1"
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
},
Upgrade to Electron 1.8.2 / Node.js 8.2.1 (#2066) * Upgrade to Electron 1.8.2 / Node.js 8.2.1 * Update CI Node.js versions * Make `engines` top-level property This was accidentally included under `build` which is disallowed by `electron-builder`. * Refactor notification updates Allows easier debugging through variable inspection. * Use `appId` for Application User Model ID Recommended in: https://github.com/electron/electron/issues/10864#issuecomment-346229090 * Update `spectron` to 3.8.0 * Bump `electron-builder` based dependencies * Use `config.extraMetadata` instead of `em` Prevents `Unknown argument: em` error. See: https://github.com/electron-userland/electron-builder/issues/2615 * Revert AUMID to be based on `packageJson.name` In our build artifact `packageJson.build.appId` causes an NPE.
2018-03-02 20:43:03 +01:00
"engines": {
Upgrade to node 10.13.0; update chokidar, its dep upath fails
2018-11-16 02:28:57 +01:00
"node": "10.13.0"
Upgrade to Electron 1.8.2 / Node.js 8.2.1 (#2066) * Upgrade to Electron 1.8.2 / Node.js 8.2.1 * Update CI Node.js versions * Make `engines` top-level property This was accidentally included under `build` which is disallowed by `electron-builder`. * Refactor notification updates Allows easier debugging through variable inspection. * Use `appId` for Application User Model ID Recommended in: https://github.com/electron/electron/issues/10864#issuecomment-346229090 * Update `spectron` to 3.8.0 * Bump `electron-builder` based dependencies * Use `config.extraMetadata` instead of `em` Prevents `Unknown argument: em` error. See: https://github.com/electron-userland/electron-builder/issues/2615 * Revert AUMID to be based on `packageJson.name` In our build artifact `packageJson.build.appId` causes an NPE.
2018-03-02 20:43:03 +01:00
},
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
"build": {
"appId": "org.whispersystems.signal-desktop",
"mac": {
Beta versions support: SxS support, in-app env/instance display (#1606) * Script for beta config; unique data dir, in-app env/type display To release a beta build, increment the version and add -beta-N to the end, then go through all the standard release activities. The prepare-build npm script then updates key bits of the package.json to ensure that the beta build can be installed alongside a production build. This includes a new name ('Signal Beta') and a different location for application data. Note: Beta builds can be installed alongside production builds. As part of this, a couple new bits of data are shown across the app: - Environment (development or test, not shown if production) - App Instance (disabled in production; used for multiple accounts) These are shown in: - The window title - both environment and app instance. You can tell beta builds because the app name, preceding these data bits, is different. - The about window - both environment and app instance. You can tell beta builds from the version number. - The header added to the debug log - just environment. The version number will tell us if it's a beta build, and app instance isn't helpful. * Turn on single-window mode in non-production modes Because it's really frightening when you see 'unable to read from db' errors in the console. * aply.sh: More instructions for initial setup and testing * Gruntfile: Get consistent with use of package.json datas * Linux: manually update desktop keys, since macros not available
2017-10-30 21:57:13 +01:00
"artifactName": "${name}-mac-${version}.${ext}",
Setup publishing to s3
2017-04-07 00:10:04 +02:00
"category": "public.app-category.social-networking",
Generate icons with electron-icon-maker Either icon-gen or local scaling of images was producing a corrupted and glitchy .icns file. With this module, we need only provide a 1024px image and it handles the scaling and generation of all other icon assets. // FREEBIE
2017-04-21 23:31:58 +02:00
"icon": "build/icons/mac/icon.icns",
Use cdn endpoint for auto update (#1538) This will make electron-updater use the cdn-fronted updates.signal.org instead of the s3 endpoint. You can verify it worked by looking at the url generated in dist/latest-mac.json and dist/win-unpacked/resources/app-update.yml // FREEBIE
2017-10-04 23:04:52 +02:00
"publish": [
{
"provider": "generic",
"url": "https://updates.signal.org/desktop"
}
],
WIP Travis build // FREEBIE
2017-05-03 20:32:20 +02:00
"target": [
"zip"
],
Reset bundleVersion
2017-05-05 03:37:29 +02:00
"bundleVersion": "1"
Setup publishing to s3
2017-04-07 00:10:04 +02:00
},
"win": {
Unpack hunspell dictionaries on windows and linux // FREEBIE
2017-05-19 00:46:47 +02:00
"asarUnpack": "node_modules/spellchecker/vendor/hunspell_dictionaries",
Beta versions support: SxS support, in-app env/instance display (#1606) * Script for beta config; unique data dir, in-app env/type display To release a beta build, increment the version and add -beta-N to the end, then go through all the standard release activities. The prepare-build npm script then updates key bits of the package.json to ensure that the beta build can be installed alongside a production build. This includes a new name ('Signal Beta') and a different location for application data. Note: Beta builds can be installed alongside production builds. As part of this, a couple new bits of data are shown across the app: - Environment (development or test, not shown if production) - App Instance (disabled in production; used for multiple accounts) These are shown in: - The window title - both environment and app instance. You can tell beta builds because the app name, preceding these data bits, is different. - The about window - both environment and app instance. You can tell beta builds from the version number. - The header added to the debug log - just environment. The version number will tell us if it's a beta build, and app instance isn't helpful. * Turn on single-window mode in non-production modes Because it's really frightening when you see 'unable to read from db' errors in the console. * aply.sh: More instructions for initial setup and testing * Gruntfile: Get consistent with use of package.json datas * Linux: manually update desktop keys, since macros not available
2017-10-30 21:57:13 +01:00
"artifactName": "${name}-win-${version}.${ext}",
Add certificate name for windows code-signing (#1513) * Add certificate name for windows code-signing electron-builder supports our extended validation code-signing cert, but only on windows. Our release process must now include a signing step on windows. FREEBIE * AppVeyor Remove certificateSubjectName to disable signing * Move code-signing disable package.json updates above build * AppVeyor: Use temporary holding file for package.json changes
2017-09-28 20:58:45 +02:00
"certificateSubjectName": "Signal",
Update electron-updater and supply it with windows/publisherName (#1535) This ensures that the signing certificate of any binary pulled down as part of auto-update on Windows is in the CA chain (not self-signed) and has the right publisherName. electron-updater also rejects any unsigned binary when asked to check the publisherName. FREEBIE
2017-10-04 23:05:23 +02:00
"publisherName": "Signal (Quiet Riddle Ventures, LLC)",
Generate icons with electron-icon-maker Either icon-gen or local scaling of images was producing a corrupted and glitchy .icns file. With this module, we need only provide a 1024px image and it handles the scaling and generation of all other icon assets. // FREEBIE
2017-04-21 23:31:58 +02:00
"icon": "build/icons/win/icon.ico",
Use cdn endpoint for auto update (#1538) This will make electron-updater use the cdn-fronted updates.signal.org instead of the s3 endpoint. You can verify it worked by looking at the url generated in dist/latest-mac.json and dist/win-unpacked/resources/app-update.yml // FREEBIE
2017-10-04 23:04:52 +02:00
"publish": [
{
"provider": "generic",
"url": "https://updates.signal.org/desktop"
}
],
CI builds and uploads all targets // FREEBIE
2017-05-06 01:28:27 +02:00
"target": [
Remove unused build assets Linux: deb (dropped zip) Mac: zip (dropped dmg) Windows: exe (dropped zip) We can always re-add if people are relying on these things. But our download links all point to these assets, so we'll generate and upload only these for now.
2018-05-01 18:47:10 +02:00
"nsis"
CI builds and uploads all targets // FREEBIE
2017-05-06 01:28:27 +02:00
]
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
},
Delete data on windows uninstall
2018-03-06 00:24:56 +01:00
"nsis": {
"deleteAppDataOnUninstall": true
},
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
"linux": {
Update builder (Windows taskbar), tweak config (GNOME taskbar) (#1473) * Update electron-builder and config, grunt-exec, and spellchecker electron-builder is a major update: ^18.8.1 -> ^19.27.3 Fixes #1463, where we lose the user's decision to pin to taskbar The other three are all minor changes, but it's generally good to stay up to date. FREEBIE * Add category for our Linux build target Fixes #1460, though the recommended list of categories doesn't seem to match what is shown in Linux Mint. Hopefully it understands that what was previously 'Networking' should now be 'Internet' Standard list: https://standards.freedesktop.org/menu-spec/latest/apa.html FREEBIE * Add StartupWMClass to .desktop file so GNOME can find running app Fixes #1432 FREEBIE
2017-09-13 22:43:00 +02:00
"category": "Network",
"desktop": {
"StartupWMClass": "Signal"
},
Unpack hunspell dictionaries on windows and linux // FREEBIE
2017-05-19 00:46:47 +02:00
"asarUnpack": "node_modules/spellchecker/vendor/hunspell_dictionaries",
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
"target": [
Remove unused build assets Linux: deb (dropped zip) Mac: zip (dropped dmg) Windows: exe (dropped zip) We can always re-add if people are relying on these things. But our download links all point to these assets, so we'll generate and upload only these for now.
2018-05-01 18:47:10 +02:00
"deb"
Add icon path for linux // FREEBIE
2017-04-28 01:57:31 +02:00
],
"icon": "build/icons/png"
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
},
Add .deb specific dependencies (#1858) Some barebones debian-based systems (e.g. Docker containers) don't come with the libasound2 and libxss1 libraries, which electron-builder does not include by default.
2017-12-14 20:32:04 +01:00
"deb": {
Support the latest phone number formats via libphonenumber (#1899) * Update to the latest google-libphonenumber * Update package.json to the format uses when updating it
2017-12-15 01:30:24 +01:00
"depends": [
"libnotify4",
"libappindicator1",
"libxtst6",
"libnss3",
"libasound2",
"libxss1"
]
Add .deb specific dependencies (#1858) Some barebones debian-based systems (e.g. Docker containers) don't come with the libasound2 and libxss1 libraries, which electron-builder does not include by default.
2017-12-14 20:32:04 +01:00
},
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
"files": [
Configure app/build using node config Add environment-specific configs under `./config` and integrate with the build system. Also changes package.json `files` from blacklist to whitelist. // FREEBIE
2017-04-10 09:22:38 +02:00
"package.json",
"config/default.json",
More release scripting in npm npm run icon-gen and grunt (run default task) can be grouped into one operation. Use SIGNAL_ENV instead of NODE_ENV since Setting NODE_ENV adversely affects yarn's install behavior, so we had to set it after the install and before the build. By using a custom variable instead, we can set it globally and eventually use it in a build matrix. Move mas build to its own npm script // FREEBIE
2017-05-05 02:26:51 +02:00
"config/${env.SIGNAL_ENV}.json",
"config/local-${env.SIGNAL_ENV}.json",
Configure app/build using node config Add environment-specific configs under `./config` and integrate with the build system. Also changes package.json `files` from blacklist to whitelist. // FREEBIE
2017-04-10 09:22:38 +02:00
"background.html",
Deployment: No longer use CI windows assets, include about.html (#1564) * Include about.html in production Electron build * Remove windows from fetch-release task, fix permissions We no longer use the pre-built assets from AppVeyor for our Windows build. * AppVeyor: Remove capture/upload of built assets
2017-10-17 17:03:47 +02:00
"about.html",
New media permission, show dialog when not enabled for voice msg UI now in separate renderer: - the permissions popup - settings dialog - debug log dialog - about window Couple bug fixes: - About Window: Fix 'escape' to close window - Remove outdated dist/copy tasks from Gruntfile Eslintified settings_view.js
2018-07-04 00:33:50 +02:00
"settings.html",
"permissions_popup.html",
"debug_log.html",
Configure app/build using node config Add environment-specific configs under `./config` and integrate with the build system. Also changes package.json `files` from blacklist to whitelist. // FREEBIE
2017-04-10 09:22:38 +02:00
"_locales/**",
"protos/*",
"js/**",
Include compiled TypeScript JavaScript files in build
2018-04-11 21:10:57 +02:00
"ts/**/*.js",
"ts/*.js",
Configure app/build using node config Add environment-specific configs under `./config` and integrate with the build system. Also changes package.json `files` from blacklist to whitelist. // FREEBIE
2017-04-10 09:22:38 +02:00
"stylesheets/*.css",
"!js/register.js",
Get standalone registration working in development Whisper.events.trigger('openStandalone') to open the standalone registration view. // FREEBIE
2017-04-19 19:34:19 +02:00
"!js/views/standalone_registration_view.js",
Refactor external source files to live in app/
2017-06-22 02:31:20 +02:00
"app/*",
Configure app/build using node config Add environment-specific configs under `./config` and integrate with the build system. Also changes package.json `files` from blacklist to whitelist. // FREEBIE
2017-04-10 09:22:38 +02:00
"preload.js",
Include about_preload.js in production builds (#2485)
2018-07-04 00:03:13 +02:00
"about_preload.js",
New media permission, show dialog when not enabled for voice msg UI now in separate renderer: - the permissions popup - settings dialog - debug log dialog - about window Couple bug fixes: - About Window: Fix 'escape' to close window - Remove outdated dist/copy tasks from Gruntfile Eslintified settings_view.js
2018-07-04 00:33:50 +02:00
"settings_preload.js",
Ensure that the production build has permissions_popup_preload.js
2018-07-12 22:03:17 +02:00
"permissions_popup_preload.js",
New media permission, show dialog when not enabled for voice msg UI now in separate renderer: - the permissions popup - settings dialog - debug log dialog - about window Couple bug fixes: - About Window: Fix 'escape' to close window - Remove outdated dist/copy tasks from Gruntfile Eslintified settings_view.js
2018-07-04 00:33:50 +02:00
"debug_log_preload.js",
Configure app/build using node config Add environment-specific configs under `./config` and integrate with the build system. Also changes package.json `files` from blacklist to whitelist. // FREEBIE
2017-04-10 09:22:38 +02:00
"main.js",
"images/**",
"fonts/*",
Add icon to the window manually on creation (#1735) This supplements the work we already do to tell the OS about our icon.
2017-11-09 02:33:20 +01:00
"build/assets",
Configure app/build using node config Add environment-specific configs under `./config` and integrate with the build system. Also changes package.json `files` from blacklist to whitelist. // FREEBIE
2017-04-10 09:22:38 +02:00
"node_modules/**",
Fix ASAR filter: takes ASAR size down by ~200MB (#1869) I knew the emoji stuff was huge, just didn't realize that our filtering for the ASAR was broken so none of our rules applied!
2017-12-06 21:44:16 +01:00
"!node_modules/emoji-panel/dist/*",
"!node_modules/emoji-panel/lib/emoji-panel-emojione-*.css",
"!node_modules/emoji-panel/lib/emoji-panel-google-*.css",
"!node_modules/emoji-panel/lib/emoji-panel-twitter-*.css",
"!node_modules/emoji-panel/lib/emoji-panel-apple-{16,20,64}.css",
"!node_modules/emoji-datasource/emoji_pretty.json",
Emoji: Eliminate unused images, make sure panel clicks add emoji (#1849) * Emoji: Ensure that all clicks work by using emoji data directly * Eliminate a number of unused emoji images from final build * Re-add the generic sheets directory, which we partially filter
2017-12-04 19:19:35 +01:00
"!node_modules/emoji-datasource/*.png",
Fix ASAR filter: takes ASAR size down by ~200MB (#1869) I knew the emoji stuff was huge, just didn't realize that our filtering for the ASAR was broken so none of our rules applied!
2017-12-06 21:44:16 +01:00
"!node_modules/emoji-datasource-apple/emoji_pretty.json",
Emoji: Eliminate unused images, make sure panel clicks add emoji (#1849) * Emoji: Ensure that all clicks work by using emoji data directly * Eliminate a number of unused emoji images from final build * Re-add the generic sheets directory, which we partially filter
2017-12-04 19:19:35 +01:00
"!node_modules/emoji-datasource-apple/img/apple/{sheets-128,sheets-256}/*.png",
"!node_modules/emoji-datasource-apple/img/apple/sheets/{16,20,32}.png",
Multi-error, multi-language, and cross-platform spell-check FREEBIE
2017-08-17 03:09:50 +02:00
"!node_modules/spellchecker/vendor/hunspell/**/*",
Exclude some files from inclusion in packaged app This adds and extends the default `files` config from electron-builder such that it adds all and only the necessary files to our app.asar. // FREEBIE
2017-03-31 00:06:41 +02:00
"!**/node_modules/*/{CHANGELOG.md,README.md,README,readme.md,readme,test,__tests__,tests,powered-test,example,examples,*.d.ts}",
"!**/node_modules/.bin",
Exclude some build files from native modules In practice this removes about 1MB of extraneous build resoures from the spellchecker module in a packaged build. // FREEBIE
2017-04-27 00:54:46 +02:00
"!**/node_modules/*/build/**",
Exclude some files from inclusion in packaged app This adds and extends the default `files` config from electron-builder such that it adds all and only the necessary files to our app.asar. // FREEBIE
2017-03-31 00:06:41 +02:00
"!**/*.{o,hprof,orig,pyc,pyo,rbc}",
"!**/._*",
Fix ASAR filter: takes ASAR size down by ~200MB (#1869) I knew the emoji stuff was huge, just didn't realize that our filtering for the ASAR was broken so none of our rules applied!
2017-12-06 21:44:16 +01:00
"!**/{.DS_Store,.git,.hg,.svn,CVS,RCS,SCCS,__pycache__,thumbs.db,.gitignore,.gitattributes,.editorconfig,.flowconfig,.yarn-metadata.json,.idea,appveyor.yml,.travis.yml,circle.yml,npm-debug.log,.nyc_output,yarn.lock,.yarn-integrity}",
"node_modules/spellchecker/build/Release/*.node",
node-sqlcipher update: always build, statically link openssl
2018-08-02 21:25:00 +02:00
"node_modules/websocket/build/Release/*.node",
Enable CI and packaged builds with Electron v3 (#2939) * Update spectron to fix linux CI runs * Point test-release grunt task at release folder * Ensure that build folders of socks/smart-buffer are in build * AppVeyor: windows build output folder is now release * Travis: Force build output to release directory
2018-11-28 01:20:48 +01:00
"node_modules/socks/build/*.js",
"node_modules/socks/build/common/*.js",
"node_modules/socks/build/client/*.js",
"node_modules/smart-buffer/build/*.js",
node-sqlcipher update: always build, statically link openssl
2018-08-02 21:25:00 +02:00
"!node_modules/@journeyapps/sqlcipher/deps/*"
Use default output dir: ./dist
2017-04-10 20:07:59 +02:00
]
Grunt preen and concat Set up grunt with tasks for: * preen - deletes unused files from bower_components, configured in bower.json * concat - concatenates preened bower components, configured automagically from the preen config It's worth noting that this setup assumes the order of files within a package doesn't matter. This is usually true since we often include only one file from the package.
2014-10-30 02:32:29 +01:00
}
}
Reference in a new issue Copy permalink