obsidian-typings 2.20.0 → 2.20.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
|
@@ -81,28 +81,6 @@ Be aware that the typings currently only cover a subset of the full API: while m
|
|
|
81
81
|
|
|
82
82
|
If you prefer not to add `obsidian-typings` to your `types`, you can also add `import 'obsidian-typings';` to any project file.
|
|
83
83
|
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
4. **Using `obsidian-typings/implementations`** <span id="using-obsidian-typings-implementations"></span>
|
|
87
|
-
|
|
88
|
-
Depending on how your project is set up, `import { X } from 'obsidian-typings/implementations';` may not work straight out of the box, e.g., if you have `"moduleResolution": "node"` or `"node10"` in your `tsconfig.json`
|
|
89
|
-
|
|
90
|
-
To solve this, you can add the following to your `tsconfig.json`:
|
|
91
|
-
|
|
92
|
-
```json
|
|
93
|
-
{
|
|
94
|
-
"compilerOptions": {
|
|
95
|
-
"...": "...",
|
|
96
|
-
"paths": {
|
|
97
|
-
"obsidian-typings/implementations": [
|
|
98
|
-
"./node_modules/obsidian-typings/dist/implementations.d.ts",
|
|
99
|
-
"./node_modules/obsidian-typings/dist/implementations.cjs"
|
|
100
|
-
]
|
|
101
|
-
}
|
|
102
|
-
}
|
|
103
|
-
}
|
|
104
|
-
```
|
|
105
|
-
|
|
106
84
|
## Usage
|
|
107
85
|
|
|
108
86
|
### `obsidian` module internals
|
package/package.json
CHANGED