fallow 3.2.0 → 3.4.2

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 CHANGED
@@ -119,7 +119,7 @@ Create a config file in your project root, or run `fallow init`:
119
119
  ```jsonc
120
120
  // .fallowrc.json
121
121
  {
122
- "$schema": "https://raw.githubusercontent.com/fallow-rs/fallow/main/schema.json",
122
+ "$schema": "./node_modules/fallow/schema.json",
123
123
  "entry": ["src/workers/*.ts", "scripts/*.ts"],
124
124
  "ignorePatterns": ["**/*.generated.ts"],
125
125
  "rules": {
@@ -130,6 +130,16 @@ Create a config file in your project root, or run `fallow init`:
130
130
  }
131
131
  ```
132
132
 
133
+ `$schema` gives editors autocomplete and validation and has no effect on
134
+ analysis. As an npm package, `fallow` always ships a version-aligned schema at
135
+ `./node_modules/fallow/schema.json`, which `fallow init` and
136
+ `fallow recommend` point at by default: offline, no editor trust prompt. If
137
+ you install fallow another way (cargo, homebrew, a bare binary) with no
138
+ `node_modules/fallow` to point at, use the remote fallback instead:
139
+ `https://raw.githubusercontent.com/fallow-rs/fallow/main/schema.json`. Some
140
+ editors, including VS Code, refuse to load a remote schema URL until you
141
+ explicitly trust the domain.
142
+
133
143
  Also supports TOML (`fallow init --toml` creates `fallow.toml`).
134
144
 
135
145
  ## Documentation