lexical 0.1.21 → 0.2.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
@@ -11,10 +11,10 @@ editor implementations to be built on top. Lexical's engine provides three main
11
11
 
12
12
  By design, the core of Lexical tries to be as minimal as possible.
13
13
  Lexical doesn't directly concern itself with things that monolithic editors tend to do – such as UI components, toolbars or rich-text features and markdown. Instead
14
- the logic for those features can be included via a plugin interface and used as and when they're needed. This ensures great extensibilty and keeps code-sizes
14
+ the logic for those features can be included via a plugin interface and used as and when they're needed. This ensures great extensibility and keeps code-sizes
15
15
  to a minimal – ensuring apps only pay the cost for what they actually import.
16
16
 
17
- For React apps, Lexical has tight intergration with React 18+ via the optional `@lexical/react` package. This package provides
17
+ For React apps, Lexical has tight integration with React 18+ via the optional `@lexical/react` package. This package provides
18
18
  production-ready utility functions, helpers and React hooks that make it seemless to create text editors within React.
19
19
 
20
20
  ## Usage
@@ -90,7 +90,7 @@ There are a few ways to update an editor instance:
90
90
  - Trigger an update with `editor.update()`
91
91
  - Setting the editor state via `editor.setEditorState()`
92
92
  - Applying a change as part of an existing update via `editor.registerNodeTransform()`
93
- - Using a command listener with `editor.registerCommand( () => {...}, priority)`
93
+ - Using a command listener with `editor.registerCommand(EXAMPLE_COMMAND, () => {...}, priority)`
94
94
 
95
95
  The most common way to update the editor is to use `editor.update()`. Calling this function
96
96
  requires a function to be passed in that will provide access to mutate the underlying
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "lexical",
3
- "description": "Lexical is an extensible text editor library that provides excellent reliability, accessible and performance.",
3
+ "description": "Lexical is an extensible text editor framework that provides excellent reliability, accessible and performance.",
4
4
  "keywords": [
5
5
  "react",
6
6
  "lexical",
@@ -9,7 +9,7 @@
9
9
  "rich-text"
10
10
  ],
11
11
  "license": "MIT",
12
- "version": "0.1.21",
12
+ "version": "0.2.2",
13
13
  "main": "Lexical.js",
14
14
  "typings": "Lexical.d.ts",
15
15
  "repository": {