Alex
Alex
You can create an action that will catch events with a different name and create new ones with the correct. ```svelte import type { Action } from "svelte/action"; export let...
The main component has updateProps and other things that are required for vanilla js. This can be moved to a separate component. In addition, it has a size of 500...
Blocked by https://github.com/josdejong/svelte-jsoneditor/issues/373
I think you can just export the svelte component and the wrapper component separately https://github.com/sveltejs/kit/discussions/8825 https://github.com/sveltejs/kit/pull/8922 https://kit.svelte.dev/docs/packaging#anatomy-of-a-package-json-exports
You can obfuscate your build. Or next to public routes, create a route with [the rest parameters](https://kit.svelte.dev/docs/advanced-routing#rest-parameters) and display the page based on them. But this is a bad practice.
I see that more tests need to be added for `getAll` and `getAllAndOverride`, as well as more type checks for all. It is better for the members to do this...
For those who used a decorator with transformation, the return type was `unknown`, and now it will become `TTransformed`. Nothing will change for the others.
Snippet with what?
I managed to launch prettier plugins by specifying them in .prettierrc
This should be in the mongoose itself, because in fact it does not track all changes