docs: plugins are explicit opt-in — correct the README scale section and plugins config comment
A clean-room install smoke of the published GA pair caught the README telling scale-up users the native provider is auto-detected. It is not, by design: the loader (loadPlugins) does no auto-detection — undefined means no plugins, and only an explicit plugins: ['@soulcraft/cor'] loads the native engine (loud failure if it can't). The stale comment on the plugins config field in the public types claimed auto-detection and is corrected to match the loader; one phrase in the plugin-author guide likewise.
This commit is contained in:
parent
99d526d394
commit
e420369850
4 changed files with 21 additions and 9 deletions
|
|
@ -70,7 +70,7 @@ export default myPlugin
|
|||
|
||||
### 2. Package exports
|
||||
|
||||
Your package must export the plugin as the default export so brainy's auto-detection works:
|
||||
Your package must export the plugin as the default export so brainy's plugin loader can resolve it:
|
||||
|
||||
```typescript
|
||||
// index.ts
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue