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

169 lines
5.7 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",
Update project/repo names in package.json // FREEBIE
2016-01-01 23:23:44 +01:00
"repository": "https://github.com/WhisperSystems/Signal-Desktop.git",
v1.0.37 Fix issue where application won't start up when /tmp is mounted noexec on Linux (#1734) Fix issue where more and more messages would be loaded on every restart (#1719) Add accelerators for top-level menu shorts, and ensure they can be localized - thanks to @cyberang3l! (#1702) Update strings for: de, el, es, es_419, fa, hi, it, no, pt_PT, ro, ru, sl, and zh_TW (#1733)
2017-11-09 01:22:20 +01:00
"version": "1.0.37",
Populate required fields in package.json // FREEBIE
2017-03-08 01:55:24 +01:00
"license": "GPL-3.0",
"author": {
"name": "Open Whisper Systems",
"email": "support@whispersystems.org"
},
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",
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
"devDependencies": {
Add asar for inspeting asar contents
2017-04-21 22:59:27 +02:00
"asar": "^0.13.0",
Build unminified manifest.css from sources
2014-11-07 09:32:32 +01:00
"bower": "^1.3.12",
Update to the latest 1.7.x electron (#1736)
2017-11-09 02:32:52 +01:00
"electron": "~1.7.9",
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
"electron-builder": "^19.27.3",
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
"electron-icon-maker": "^0.0.3",
Show dialog box when there's an update for download
2017-06-09 21:37:01 +02:00
"electron-publisher-s3": "^19.0.1",
Upgrade dev dependencies Including multiple major version upgrades. // FREEBIE
2017-04-21 11:40:06 +02:00
"grunt": "^1.0.1",
"grunt-cli": "^1.2.0",
"grunt-contrib-concat": "^1.0.1",
"grunt-contrib-copy": "^1.0.0",
Update jshint
2017-04-19 01:46:02 +02:00
"grunt-contrib-jshint": "^1.1.0",
Upgrade dev dependencies Including multiple major version upgrades. // FREEBIE
2017-04-21 11:40:06 +02:00
"grunt-contrib-watch": "^1.0.0",
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
"grunt-exec": "^3.0.0",
Add build support for expiring old releases Builds expire after 90 days.
2016-04-04 04:34:34 +02:00
"grunt-gitinfo": "^0.1.7",
Upgrade dev dependencies Including multiple major version upgrades. // FREEBIE
2017-04-21 11:40:06 +02:00
"grunt-jscs": "^3.0.1",
Switch to grunt-sass + node-sass-import-once These modules together allow us to import css files from third party components without maintaining symlinks that essentially rename them as sass partials, which doesn't work on windows. // FREEBIE
2017-05-04 01:43:36 +02:00
"grunt-sass": "^2.0.0",
Add spectron
2017-05-06 06:39:04 +02:00
"node-sass-import-once": "^1.2.0",
"spectron": "^3.6.2"
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",
Run tests on Sauce Labs * Issue #57
2014-11-23 04:36:52 +01:00
"test": "grunt test",
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
"lint": "grunt jshint",
Configure electron-builder // FREEBIE
2017-03-10 19:35:58 +01:00
"start": "electron .",
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
"asarl": "asar l release/mac/Signal.app/Contents/Resources/app.asar",
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",
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
"generate": "npm run icon-gen && grunt",
"build": "build --em.environment=$SIGNAL_ENV",
"dist": "npm run generate && npm run build",
script to build for electron on install, Electron docs refresh (#1491) * Add new postinstall script for automatic electron builds FREEBIE * Documentation refresh for the world of electron FREEBIE
2017-09-20 00:31:04 +02:00
"pack": "npm run generate && npm run build -- --dir",
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
"prepare-build": "node prepare_build.js",
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
"pack-prod": "SIGNAL_ENV=production npm run pack",
"dist-prod": "SIGNAL_ENV=production npm run dist",
"dist-prod-all": "SIGNAL_ENV=production npm run dist -- -mwl",
"build-release": "SIGNAL_ENV=production npm run build -- --config.directories.output=release",
"build-mas-release": "npm run build-release -- -m --config.mac.target=mas",
Add spectron
2017-05-06 06:39:04 +02:00
"build-mas-dev": "npm run build-release -- -m --config.mac.target=mas --config.type=development",
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
"prep-mac-release": "npm run build-release -- -m --dir",
Restructure prep-release script slightly Order of operations is now: - regenerate local assets - clean the release dir - download linux/windows releases - build osx release - smoke all test releases // FREEBIE
2017-05-08 19:29:42 +02:00
"prep-release": "npm run generate && grunt prep-release && npm run build-release && npm run build-mas-release && grunt test-release",
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
"release-mac": "npm run build-release -- -m --prepackaged release/mac/Signal.app --publish=always",
Update our release scripts to match changes in electron-builder (#1484) No more win-unpacked/linux-unpacked, so we need to extract downloaded zips into their own folders manually. FREEBIE
2017-09-19 00:51:01 +02:00
"release-win": "npm run build-release -- -w --prepackaged release/windows --publish=always",
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
"release-lin": "npm run build-release -- -l --prepackaged release/linux && NAME=$npm_package_name VERSION=$npm_package_version ./aptly.sh",
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
"release": "npm run release-mac && npm run release-win && npm run release-lin"
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"
},
{
"provider": "s3",
"region": "us-east-1",
"bucket": "updates.signal.org",
"path": "desktop",
"acl": "public-read"
}
],
WIP Travis build // FREEBIE
2017-05-03 20:32:20 +02:00
"target": [
"dmg",
"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"
},
{
"provider": "s3",
"region": "us-east-1",
"bucket": "updates.signal.org",
"path": "desktop",
"acl": "public-read"
}
],
CI builds and uploads all targets // FREEBIE
2017-05-06 01:28:27 +02:00
"target": [
"nsis",
"zip"
]
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": [
CI builds and uploads all targets // FREEBIE
2017-05-06 01:28:27 +02:00
"deb",
"zip"
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
},
"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",
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/**",
"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",
"main.js",
"audio/**",
"images/**",
"fonts/*",
"node_modules/**",
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/**",
"**/node_modules/*/build/**/*.node",
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}",
"!**/._*",
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
"!**/{.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}"
Use default output dir: ./dist
2017-04-10 20:07:59 +02:00
]
Auto-update hourly
2017-03-30 20:43:58 +02:00
},
"dependencies": {
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
"bunyan": "^1.8.12",
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
"config": "^1.26.2",
Introduce new dependency for user settings: electron-config FREEBIE
2017-05-22 18:21:47 +02:00
"electron-config": "^1.0.0",
Add spellcheck As of Electron 1.6.5, this requires disabling the sandbox in order to get access to the `webFrame` api. // FREEBIE
2017-04-20 00:25:03 +02:00
"electron-editor-context-menu": "^1.1.1",
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
"electron-updater": "^2.9.3",
Upgrade emoji support (#1482) * Upgrade emoji deps and move to node_modules Add support for Emoji 3.0 and switch from bower to yarn for managing emoji dependencies. // FREEBIE * Delete old emoji deps // FREEBIE * Don't copy emoji on windows It is no longer necessary since the symlinked image dir is gone. // FREEBIE * Update emoji test // FREEBIE * Fix emoji tests; remove all overrides of emoji-js functions FREEBIE
2017-09-15 22:22:11 +02:00
"emoji-datasource-apple": "^3.0.0",
"emoji-js": "^3.2.2",
Emoji picker (#1608) * Add emoji button and popup panel This integrates a simple third party emoji panel with a few css overrides to correct some relative paths and colors. The trickiest thing about this is ensuring we don't break the layout, which is acheived through precise control over the panel's height, and prodigious calls to updateMessageFieldSize. // FREEBIE * Don't close emoji panel on click, do close on send To better facilitate multiple emoji entry. // FREEBIE * Make panel emojis bigger and higher resolution // FREEBIE * Move paperclip button to the right of the microphone This makes our bottom-bar button arrangement more comfortable and consistent with Android. // FREEBIE * Move emoji picker padding to inner container * Insert emojis at cursor position Don't just append to the end like a n00b! Also handle selected text correctly. https://stackoverflow.com/questions/11076975 // FREEBIE * A few visual tweaks to reduce visual complexity of emoji panel - No gray buffer on the right side of the emoji panel - No gray buffer between message compose text box and emoji window - The scroll bar for the emojis is the same as our normal scrollbars
2017-10-30 21:54:55 +01:00
"emoji-panel": "^0.5.2",
Update libphonenumber (#1598) * Update libphonenumber Also switch from bower to yarn for managing this dependency. // FREEBIE * Remove libphonenumber from bower.json // FREEBIE
2017-10-30 22:45:57 +01:00
"google-libphonenumber": "^3.0.7",
Add lodash for server-side utility functions FREEBIE
2017-08-17 19:51:37 +02:00
"lodash": "^4.17.4",
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
"mkdirp": "^0.5.1",
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-21 00:52:02 +02:00
"node-fetch": "^1.7.3",
Add os-locale to reliably get xx-XX style locale on all OSes FREEBIE
2017-08-17 01:47:32 +02:00
"os-locale": "^2.1.0",
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
"rimraf": "^2.6.2",
Add semver and spellchecker directly, remove electron-provider FREEBIE
2017-08-16 18:29:43 +02:00
"semver": "^5.4.1",
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
"spellchecker": "^3.4.3",
Certificate pinning via node XMLHttpRequest implementation (#1394) * Add certificate pinning on https service requests Make https requests to the server using node apis instead of browser apis, so we can specify our own CA list, which contains only our own CA. This protects us from MITM by a rogue CA. As a bonus, this let's us drop the use of non-standard ports and just use good ol' default 443 all the time, at least for http requests. // FREEBIE * Make certificateAuthorities an option on requests Modify node-based xhr implementation based on driverdan/node-XMLHttpRequest, adding support for setting certificate authorities on each request. This allows us to pin our master CA for requests to the server and cdn but not to the s3 attachment server, for instance. Also fix an exception when sending binary data in a request: it is submitted as an array buffer, and must be converted to a node Buffer since we are now using a node based request api. // FREEBIE * Import node-based xhr implementation Add a copy of https://github.com/driverdan/node-XMLHttpRequest@86ff70e, and expose it to the renderer in the preload script. In later commits this module will be extended to support custom certificate authorities. // FREEBIE * Support "arraybuffer" responseType on requests When fetching attachments, we want the result as binary data rather than a utf8 string. This lets our node-based XMLHttpRequest honor the responseType property if it is set on the xhr. Note that naively using the raw `.buffer` from a node Buffer won't work, since it is a reuseable backing buffer that is often much larger than the actual content defined by the Buffer's offset and length. Instead, we'll prepare a return buffer based on the response's content length header, and incrementally write chunks of data into it as they arrive. // FREEBIE * Switch to self-signed server endpoint * Log more error info on failed requests With the node-based xhr, relevant error info are stored in statusText and responseText when a request fails. // FREEBIE * Add node-based websocket w/ support for custom CA // FREEBIE * Support handling array buffers instead of blobs Our node-based websocket calls onmessage with an arraybuffer instead of a blob. For robustness (on the off chance we switch or update the socket implementation agian) I've kept the machinery for converting blobs to array buffers. // FREEBIE * Destroy all wacky server ports // FREEBIE
2017-09-01 17:58:58 +02:00
"websocket": "^1.0.24"
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