Gathering detailed insights and metrics for lexical-svelte-runes
Gathering detailed insights and metrics for lexical-svelte-runes
Gathering detailed insights and metrics for lexical-svelte-runes
Gathering detailed insights and metrics for lexical-svelte-runes
npm install lexical-svelte-runes
Typescript
Module System
Node Version
NPM Version
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
28
7
44
the main check test branch
i forked lexical repo for tracking purpose fork, ideally we need to catch up commit by commit by i guess it is fine that we just add whatever is needed.
1pnpm install lexical-svelte-runes@latest @unocss/reset
1<script lang="ts"> 2 import '@unocss/reset/tailwind-compat.css'; //using unocss reset 3 //import 'uno.css'; 4 import 'lexical-svelte-runes/uno.css'; // import all the generated classname, if you have uno or tailwind, you can ignore this 5 import 'lexical-svelte-runes/index.css'; // react playground css 6 import * as Editor from 'lexical-svelte-runes/editor'; 7 8 import { createHistoryContext } from 'lexical-svelte-runes/playground/context/SharedHistoryContext.js'; 9 import type { Settings } from 'lexical-svelte-runes/playground/appSettings.js'; 10 11 let { ...props }: Settings = $props(); // check Settings type for all the settings! 12 13 createHistoryContext(); 14</script> 15 16<Editor.SettingsContext settings={props}> 17 <Editor.SharedAutocompleteContext> 18 <Editor.LexicalComposer> 19 <div class="editor-shell w-full"> 20 <Editor.Editor /> 21 </div> 22 </Editor.LexicalComposer> 23 </Editor.SharedAutocompleteContext> 24</Editor.SettingsContext> 25 26 27
when importing a new plugin to lexical-svelte-runes, we can use external library instead of copy all the logic from react playground to keep code clean but at the same time we want to 'make sure the structure of our code is similar to react's so that it is easy to debug/maintain, a lot of times we can simply check the commits in rect to copy the changes over.
/dialog
node.svelte
plugin.svelte.ts
const [fn,setFn]=useState()
are both function just like solidjs(we also need to refractor the current repo, i.e move all plugins in to the same folder currently there are some naughty plugins outside )
src/playground/plugins/_
, unlike react repo, we want to group by features, so all required files for a feature should be under src/plugins/_, dont need to create a separate nodes folder for nodes.tsx
and .ts
files under plugins/* , slowly convert each one to svelte files , for .ts
you probably just need to fix the errors due to our svelte hooks !$
in svelte filesNo vulnerabilities found.
No security vulnerabilities found.