satori 0.10.3 → 0.10.5
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 +1 -1
- package/dist/index.cjs +5 -5
- package/dist/index.cjs.map +1 -1
- package/dist/index.js +5 -5
- package/dist/index.js.map +1 -1
- package/dist/index.wasm.cjs +5 -5
- package/dist/index.wasm.cjs.map +1 -1
- package/dist/index.wasm.js +5 -5
- package/dist/index.wasm.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -401,7 +401,7 @@ Overall there are many trade-offs between each choice, and it's better to pick t
|
|
|
401
401
|
|
|
402
402
|
By default, Satori renders the text as `<path>` in SVG, instead of `<text>`. That means it embeds the font path data as inlined information, so succeeding processes (e.g. render the SVG on another platform) don’t need to deal with font files anymore.
|
|
403
403
|
|
|
404
|
-
You can turn off this behavior by setting `
|
|
404
|
+
You can turn off this behavior by setting `embedFont` to `false`, and Satori will use `<text>` instead:
|
|
405
405
|
|
|
406
406
|
```jsx
|
|
407
407
|
const svg = await satori(
|