You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+22-11
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,15 @@
1
-
## v3.1.0 <sup>xx.xx.2022</sup>
1
+
## v3.1.2 <sup>XX.XX.2023</sup>
2
+
3
+
## v3.1.1 <sup>XX.10.2023</sup>
4
+
* Fix issue with single instance, which causes error with opening already opened app on windows
5
+
* Fixes for devEnvSetup.js
6
+
* Fix: do not download new version when desktopHCP is set to false
7
+
* Dynamically get preset-env version
8
+
* Fix addition of desktop script
9
+
* Don't SIGKILL Meteor when a desktop build terminates normally
10
+
* Fix integration tests
11
+
12
+
## v3.1.0 <sup>09.03.2022</sup>
2
13
* Updated Electron to v11
3
14
4
15
## v3.0.1 <sup>12.04.2022</sup>
@@ -47,15 +58,15 @@ Now you are free to use any version with your meteor project. Just add them to y
47
58
If you will not, `meteor-desktop` adds the recommended versions automatically when needed.
48
59
49
60
From now every `meteor-desktop` release will provide a recommended versions numbers of these dependencies.
50
-
By default I will try to make `meteor-desktop` compatible within the compatibility version of the recommended version i.e. if the recommended electron version is `2.0.10` you should still be able to use any `2.x.x` version without problems.
61
+
By default, I will try to make `meteor-desktop` compatible within the compatibility version of the recommended version i.e. if the recommended electron version is `2.0.10` you should still be able to use any `2.x.x` version without problems.
* support for Squirrel autoupdate mechanism ended, if you wish to continue with it, add the `electron-builder-squirrel-windows` dependency to your `devDependencies` and move it's settings to `squirrel` section in settings i.e.:
69
+
* support for Squirrel autoupdate mechanism ended, if you wish to continue with it, add the `electron-builder-squirrel-windows` dependency to your `devDependencies` and move its settings to `squirrel` section in settings i.e.:
@@ -109,7 +120,7 @@ You do not have to put the whole line, just any part of it that should only be f
109
120
110
121
**FIXES**
111
122
* fix [#165](https://github.com/wojtkowiak/meteor-desktop/issues/174) `meteor://` protocol is now registered as secure origin
112
-
* `bundler` caching was disabled for production builds as you might have accidentally get a development `desktop.asar` build into your production build
123
+
* `bundler` caching was disabled for production builds as you might have accidentally got a development `desktop.asar` build into your production build
113
124
114
125
## v1.0.0 <sup>21.05.2018</sup>
115
126
Meteor App serving mechanism was changed to utilise `registerStreamProtocol` and serve
@@ -121,7 +132,7 @@ Please verify thoroughly if your app is working fine after this change and repor
121
132
122
133
The localstorage contents will be migrated if you are updating your app from pre `1.0.0`.
123
134
124
-
However if you are using the `meteor-desktop-localstorage` plugin you have to make a migration yourself. The easiest way is to copy the plugin desktop code as your module in `.desktop` and on your app start get the contents with `getAll` and save them to the browser's localstorage.
135
+
However, if you are using the `meteor-desktop-localstorage` plugin you have to make a migration yourself. The easiest way is to copy the plugin desktop code as your module in `.desktop` and on your app start get the contents with `getAll` and save them to the browser's localstorage.
125
136
126
137
* [`electron`](https://github.com/electron/electron) was updated to `2.0.1`
127
138
* `MD_LOG_LEVEL` is now respected
@@ -223,7 +234,7 @@ However if you are using the `meteor-desktop-localstorage` plugin you have to ma
223
234
* **DEPRECATIONS**:
224
235
- building for `squirrel.windows` is not encouraged and from `1.0.0` the default Windows target will be `nsis`
225
236
226
-
it's more than sure that you will have to update your [`electron-builder`](https://github.com/electron-userland/electron-builder)/[`electron-packager`](https://github.com/electron-userland/electron-packager) configuration since it's a big shift from the old versions, create a new meteor project with blank scaffold (`npm run desktop -- init`) and take a look a the new `settings.json` as that might give you some hints
237
+
it's more than sure that you will have to update your [`electron-builder`](https://github.com/electron-userland/electron-builder)/[`electron-packager`](https://github.com/electron-userland/electron-packager) configuration since it's a big shift from the old versions, create a new meteor project with blank scaffold (`npm run desktop -- init`) and take a look at the new `settings.json` as that might give you some hints
227
238
228
239
#### v0.11.3 <sup>17.01.2018</sup>
229
240
- added `desktopHCPCompatibilityVersion` setting to restore ability to override desktopHCP compatibility version
@@ -251,7 +262,7 @@ it's more than sure that you will have to update your [`electron-builder`](https
251
262
252
263
## v0.8.0 <sup>05.07.2017</sup>
253
264
254
-
- added `builderCliOptions` that allow you to specify additional electron-builder CLI options e.g
265
+
- added `builderCliOptions` that allow you to specify additional electron-builder CLI options e.g.
255
266
for publishing artifacts (thanks to [ramijarrar](https://github.com/ramijarrar), related
Copy file name to clipboardexpand all lines: README.md
+38-41
Original file line number
Diff line number
Diff line change
@@ -27,27 +27,27 @@ To migrate from the original `meteor-desktop`:
27
27
28
28
## Prerequisites
29
29
30
-
- Meteor >= `1.4`
30
+
- Meteor >= `1.12.1`
31
31
- at least basic [Electron](http://electron.atom.io/) framework knowledge
32
32
- mobile platform added to project<sup>__*1__</sup>
33
33
34
34
<sup>__*1__ you can always build with `--server-only` if you do not want to have mobile clients, you do not actually have to have android sdk or xcode to go on with your project</sup>
*[Testing desktop app and modules](#testing-desktop-app-and-modules)
135
134
*[MD_LOG_LEVEL](#md_log_level)
136
135
*[Packaging](#packaging)
@@ -238,7 +237,6 @@ field|description
238
237
`version`|version of the desktop app
239
238
`projectName`|this will be used as a `name` in the generated app's package.json
240
239
`devTools`|whether to install and open `devTools`, set automatically to false when building with `--production`
241
-
`devtron`|check whether to install [`devtron`](http://electron.atom.io/devtron/), set automatically to false when building with `--production`, [more](#devtron)
242
240
`singleInstance`|sets the single instance mode - [more](https://github.com/electron/electron/blob/master/docs/api/app.md#appmakesingleinstancecallback)
243
241
`desktopHCP`|whether to use `.desktop` hot code push module - [more](#desktophcp---desktop-hot-code-push)
244
242
<sup>`desktopHCPIgnoreCompatibilityVersion`</sup>|ignore the `.desktop` compatibility version and install new versions even if they can be incompatible
@@ -489,9 +487,6 @@ not updated, nor checked for changes!
489
487
in `.desktop` will not trigger rebuilds, in that case you need to make any
490
488
change in `version` field in the `desktop.version` to trigger rebuild (this file is in the root of
491
489
your project) - this can be any change like just adding random char to the hash
492
-
- if your run a production build of your desktop app it will not receive updates from project run
493
-
from `meteor` command unless you run it with `--production` - that is because development build
494
-
has `devtron` added and therefore the `compatibilityVersion` is different
495
490
- after reload logs will no longer be shown in the console
No matter which method below you choose, run `npm run build-watch` in your local meteor-desktop folder before making changes to the code, if you want them reflected in Meteor apps that depend on the package.
594
+
595
+
### Using devEnvSetup.js
596
+
To help you contribute, there is a development environment setup script. It also runs default tests.
597
+
598
+
This script assumes you have `npm`, `git` and `meteor` available from the command line. Note that by default, the script will install packages in the *parent* directory of where it is, so it is recommended to clone meteor-desktop inside an empty dir.
This script assumes you have `npm`, `git` and `meteor` available from the command line.
616
-
617
-
Currently this package does not work when linked with `npm link`. To set up your dev environment
618
-
it is best to create a clean `Meteor` project, add `@meteor-community/meteor-desktop` to dependencies with a relative
619
-
path to the place where you have cloned this repo and in scripts add `desktop` with `node
620
-
./path/to/meteor-desktop/dist/bin/cli.js`.
621
-
Also to make changes in the desktop HCP plugins run `Meteor` project with `METEOR_PACKAGE_DIRS`
622
-
set to `/absolute/path/to/meteor-desktop/plugins` so that they will be taken from the cloned repo.
607
+
608
+
### Without using devEnvSetup.js
609
+
610
+
1. Clone and install meteor-desktop as above
611
+
2. From a clean Meteor project, install meteor-desktop from its local folder: `meteor npm i --save-dev /path/to/meteor-desktop` (doesn't work with npm link, tbc)
612
+
3. In your Meteor app's `package.json`:
613
+
1. Add a script `desktop` with `METEOR_PACKAGE_DIRS=/path/to/meteor-desktop/plugins node /path/to/meteor-desktop/dist/bin/cli.js`
614
+
2. Add `METEOR_PACKAGE_DIRS=/path/to/meteor-desktop/plugins` to the `start` script as well.
615
+
616
+
The last step is so that the desktop HCP Meteor packages are also taken from your local meteor-desktop repo.
617
+
Make sure to run Meteor with `meteor npm start` rather than just `meteor`.
618
+
619
+
Finally, follow the above "Quick start" steps (except the npm install) from your Meteor app.
0 commit comments