next-issue 1.0.5 → 1.0.6
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 +2 -1
- package/dist/config.mjs +5 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -233,7 +233,8 @@ adds `.next-issue/` to `.gitignore`. It stops when the config file is there
|
|
|
233
233
|
already; `--force` replaces it. The file holds no `setupCommand`, because the
|
|
234
234
|
harness deduces one from the lock file of the project.
|
|
235
235
|
|
|
236
|
-
|
|
236
|
+
With no file, every field keeps its default. A field that is not in the file
|
|
237
|
+
keeps its default. A file that cannot be read, a file that is not valid
|
|
237
238
|
JSON, a field with a value of the wrong type and a field name that the harness
|
|
238
239
|
does not know all stop the run, so a typo cannot pass without a word.
|
|
239
240
|
|
package/dist/config.mjs
CHANGED
|
@@ -73,8 +73,11 @@ export async function loadConfig(root) {
|
|
|
73
73
|
try {
|
|
74
74
|
raw = await readFile(join(root, CONFIG_FILE), "utf8");
|
|
75
75
|
}
|
|
76
|
-
catch {
|
|
77
|
-
|
|
76
|
+
catch (error) {
|
|
77
|
+
if (error.code === "ENOENT") {
|
|
78
|
+
return defaults();
|
|
79
|
+
}
|
|
80
|
+
throw new Error(`${CONFIG_FILE} cannot be read: ${message(error)}`);
|
|
78
81
|
}
|
|
79
82
|
let parsed;
|
|
80
83
|
try {
|