@maka/meteor-sdk 0.1.2 → 0.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +23 -8
- package/isopackets/combined/npm/node_modules/meteor/babel-compiler/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/boilerplate-generator/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/constraint-solver/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/ddp-client/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/ecmascript/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/ecmascript-runtime/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/ecmascript-runtime-client/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/ecmascript-runtime-server/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/fetch/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/inter-process-messaging/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/logging/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/logic-solver/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/meteor/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/modules/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/modules-runtime/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/npm-mongo/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/package-version-parser/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/promise/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/react-fast-refresh/node_modules/.package-lock.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/socket-stream-client/node_modules/.package-lock.json +1 -1
- package/package.json +1 -1
- package/isopackets/combined/npm/node_modules/meteor/promise/node_modules/promise/.meteor-portable-2.json +0 -1
package/README.md
CHANGED
|
@@ -29,8 +29,8 @@ const project = await sdk.loadProject("/path/to/app");
|
|
|
29
29
|
const result = await sdk.bundle(project, { outputPath: "/path/to/output" });
|
|
30
30
|
console.log(result.starManifest);
|
|
31
31
|
|
|
32
|
-
|
|
33
|
-
|
|
32
|
+
process.exit(0); // simplest way to end a one-shot script -- see close()
|
|
33
|
+
// below if your process needs to keep running afterward
|
|
34
34
|
```
|
|
35
35
|
|
|
36
36
|
## API
|
|
@@ -123,12 +123,27 @@ const result = await sdk.create("/path/to/new-app", {
|
|
|
123
123
|
### `close()`
|
|
124
124
|
|
|
125
125
|
Releases file-watch resources opened by `loadProject()`/`bundle()`/etc.
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
126
|
+
|
|
127
|
+
**For a one-shot script/CLI command that's about to exit anyway, prefer
|
|
128
|
+
skipping `close()` entirely and calling `process.exit()` directly once
|
|
129
|
+
your work is done**, rather than `await`ing `close()` first -- verified
|
|
130
|
+
to sidestep the issue below cleanly, with no downside for a process that
|
|
131
|
+
isn't doing anything else afterward. `close()` still exists for
|
|
132
|
+
longer-lived embedders that need to release watch handles mid-process
|
|
133
|
+
without exiting.
|
|
134
|
+
|
|
135
|
+
If you do call it: with the default native watcher backend, the process
|
|
136
|
+
can occasionally hang on Windows due to a `@parcel/watcher` native-addon
|
|
137
|
+
limitation outside this package's control (its background thread doesn't
|
|
138
|
+
release on `unsubscribe()`, and its public API has no lower-level
|
|
139
|
+
shutdown hook) -- and, observed specifically when the host process is
|
|
140
|
+
launched from Git Bash/MSYS2 on Windows (not from PowerShell/cmd), that
|
|
141
|
+
same untorn-down thread can crash the process outright (`SIGSEGV`)
|
|
142
|
+
during teardown instead of just hanging. Workarounds, in addition to
|
|
143
|
+
skipping `close()` above: call `process.exit()` after `close()` resolves
|
|
144
|
+
regardless of whether it hangs, or set `METEOR_MODERN='{"watcher":false}'`
|
|
145
|
+
to use the plain polling watcher instead, which doesn't exhibit either
|
|
146
|
+
symptom.
|
|
132
147
|
|
|
133
148
|
### Events
|
|
134
149
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@maka/meteor-sdk",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.3",
|
|
4
4
|
"description": "Programmatic Node API over the Meteor build tool (bundle/run/create/etc.) -- for driving Meteor's build system from plain Node code instead of shelling out to a meteor CLI (there isn't one anymore; see README.md). \"dependencies\" is generated by scripts/write-tool-package-json.js from scripts/dev-bundle-tool-package.js at the monorepo root -- do not hand-edit that field, edit that file and re-run the script instead.",
|
|
5
5
|
"main": "src/index.js",
|
|
6
6
|
"exports": {
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
true
|