You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+32-14Lines changed: 32 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@
30
30
</a>
31
31
</p>
32
32
33
-
##Key Features
33
+
# Key Features
34
34
35
35
1.**_Logical Sides in Mind:_** Figma plugins that render a UI work on two different processes (split into code.js and index.html in Figma docs). This boilerplate keeps the sides separated by allowing them to share code (under ./src/common/).
36
36
@@ -40,32 +40,46 @@
40
40
41
41
4.**_Bundled into One File:_** Figma plugins only accept a single file for `main` (js) and `ui` (html), which makes deployment of multiple files linked to each other impossible. This boilerplate is configured to bundle/inline most of the things you need like rasterize/vector image asset imports, CSS URL statements, and of course, source code imports.
42
42
43
-
5.**_SVG as Component:_** Yes, you can import SVGs as inlined sources with `*.svg?inline`, but what about actually importing them as React components? Easy! You can import an SVG file as a React component with `*.svg?react` (See `/src/ui/app.tsx` for examples)
43
+
5.**_SVG as Component:_** Yes, you can import SVGs as inlined sources with `*.svg?url`, but what about actually importing them as React components? Easy! You can import an SVG file as a React component with `*.svg?component` (See `/src/ui/app.tsx` for examples) (Using the [vite-plugin-react-rich-svg](https://github.com/iGoodie/vite-plugin-react-rich-svg) plugin)
44
44
45
45
6.**_Sassy:_** A classic, this boilerplate supports Sass/Scss/Less and modules! Check out `/src/ui/styles/` for 7-1 Sass Template and `/src/ui/components/Button.module.scss` for module examples.
46
46
47
-
##How to start coding?
47
+
# How to start coding?
48
48
49
49
1. First thing after you clone should be to install the dependencies by executing:
50
50
51
51
```
52
-
npm i
52
+
npm install
53
53
```
54
54
55
55
2. Create a figma plugin. In Figma, right click while you're in a design file. Follow `Plugins > Development > New Plugin...`. You can also type `"New Plugin...` to the global search (Windows: <kbd>CTRL</kbd> + <kbd>P</kbd>, Mac: <kbd>⌘ Command</kbd> + <kbd>P</kbd>)
56
56
3. Follow the steps on opened window. I recommend using `Default` or `Run once` layout, because you'll only need to save the manifest (for the plugin id it generates). Click "Save as", and save it to a temporary place. Then click "Open folder" to navigate to the folder it generated
57
57
4. Note down the `id` field from the `manifest.json` it generated.
58
58
5. Go to `figma.manifest.ts`, and replace the `id` with the id you noted down. Then configure the manifest there as you like. (See [Official Figma Plugin Manifest doc](https://www.figma.com/plugin-docs/manifest/))
59
59
60
-
###Developing UI
60
+
## Developing
61
61
62
-
Since UI is powered by Vite + React, you can use your browser to code the UI with HMR but **without** the figma context. Just run the following command line:
62
+
Development is very straight forward. Just run the dev command, and it will start compiling your files as you code.
63
63
64
64
```
65
-
npm start
65
+
npm run dev
66
66
```
67
67
68
-
### Building
68
+
Once dev is ran, `dist/` folder will be created, which includes your `manifest.json`. You can load it in Figma, by `Right Click > Plugins > Development > Import plugin from manifest...`
69
+
70
+
**Tip:** You can turn on the `Hot reload plugin` option in Figma, to automatically reload when files in `dist/` changes.
71
+
72
+
### Developing without Figma Context
73
+
74
+
If you like developing your UI first, then integrating with Figma context; you can run your UI code in browser just like your every other Vite project by running:
75
+
76
+
```
77
+
npm run dev:ui-only
78
+
```
79
+
80
+
Remember: since Figma context is not available in "ui-only" mode, any attempt to Figma API/SDK calls will look like a crash on your inspector/console.
81
+
82
+
## Building
69
83
70
84
Building with the following command line will yield with a `dist` folder, which is ready to be used by Figma:
71
85
@@ -75,7 +89,7 @@ npm run build
75
89
76
90
`dist/manifest.json` then can be used to load the plugin. In Figma, right click while you're in a design file. Follow `Plugins > Development > Import plugin from manifest...`. You can also type `"Import plugin from manifest...` to the global search (Windows: <kbd>CTRL</kbd> + <kbd>P</kbd>, Mac: <kbd>⌘ Command</kbd> + <kbd>P</kbd>). Then select `dist/manifest.json`
77
91
78
-
###Publishing
92
+
## Publishing
79
93
80
94
After building, built `dist` folder is going to contain every artifact you need in order to publish your plugin. Just build, and follow [Figma's Official Post on Publishing Plugins](https://help.figma.com/hc/en-us/articles/360042293394-Publish-plugins-to-the-Figma-Community#Publish_your_plugin).
81
95
@@ -87,22 +101,26 @@ After building, built `dist` folder is going to contain every artifact you need
87
101
-`src/plugin/` : Sources of the plugin logical side. Place everything that interracts with figma here.
88
102
-`src/ui/` : Sources of the ui logical side, a classical Vite + React source base.
89
103
-`scripts`
90
-
-`scripts/vite/` : Some custom vite plugins to assist inlining assets
104
+
-`scripts/vite/` : Potential custom vite plugins written for your project
105
+
-`scripts/windows/` : Potential custom Windows OS scripts
106
+
-`scripts/macos/` : Potential custom Mac OS scripts
91
107
-`figma.manifest.ts` - A module that exports [Figma Plugin Manifest](https://www.figma.com/plugin-docs/manifest/) for the build scripts
92
108
93
-
##Caveats
109
+
# Caveats
94
110
95
-
### 1. Make sure to either inline or component SVG imports!
111
+
### 1. Make sure to import SVGS as either component, url or raw!
96
112
97
113
Importing image assets other than `.svg` is easy. However, when you are importing `.svg`, by default it will load as a base64 data-uri, to import as a React component, you must add the query string `?react`.
98
114
99
115
```tsx
100
-
importMyImagefrom"@ui/assets/my_image.svg?react"; // Import as React component
101
-
importmyImagefrom"@ui/assets/my_image.svg"; // Import as base64 data-uri
0 commit comments