lucid-package 0.0.4 → 0.0.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 +5 -8
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -45,20 +45,17 @@ To start the debug server:
|
|
|
45
45
|
npx lucid-package test-editor-extension my-extension-name
|
|
46
46
|
```
|
|
47
47
|
|
|
48
|
-
You then
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
When you turn on that option, the page will refresh and your extension code will run.
|
|
48
|
+
You can then enable loading of your local plugin in the Developer menu in Lucidchart
|
|
49
|
+
by clicking `Load local extension`. The page will refresh and your extension code will run.
|
|
53
50
|
|
|
54
51
|
The main entry point to your new editor extension is in `editorextensions/my-extension-name/src/extension.ts`.
|
|
55
52
|
Experiment by changing code in that file and refreshing your browser tab to reload it.
|
|
56
53
|
|
|
57
54
|
For all published extensions, and by default for this debug server as well, your code
|
|
58
55
|
runs in a sandboxed JavaScript VM for security. However, this makes debugging difficult.
|
|
59
|
-
If you turn on the `Debug local extensions (no sandbox)` option
|
|
60
|
-
run via a scoped `eval`, allowing you to use the standard browser
|
|
61
|
-
and step through your code.
|
|
56
|
+
If you turn on the `Debug local extensions (no sandbox)` option in the Developer menu,
|
|
57
|
+
your code will be run via a scoped `eval`, allowing you to use the standard browser
|
|
58
|
+
debugging tools to examine and step through your code.
|
|
62
59
|
|
|
63
60
|
We recommend that you do all final validation of your extension with the normal
|
|
64
61
|
sandbox enabled, however, as you may have inadvertently used features not allowed in
|