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: packages/create-vue-lib/src/template/base/examples/packages/@projectName@/src/components/ExampleComponent.vue.ejs
Copy file name to clipboardExpand all lines: packages/create-vue-lib/src/template/base/examples/packages/@projectName@/src/components/MyPanelSection.vue.ejs
<spanclass="check">✔</span> <ahref="#include-tailwind-css">Include Tailwind CSS? … No / Yes</a>
47
48
<spanclass="check">✔</span> <ahref="#include-eslint">Include ESLint? … No / Yes</a>
48
49
<spanclass="check">✔</span> <ahref="#include-eslint-stylistic">Include ESLint Stylistic for formatting? … No / Yes</a>
49
50
<spanclass="check">✔</span> <ahref="#include-vitest">Include Vitest for testing? … No / Yes</a>
50
51
<spanclass="check">✔</span> <ahref="#include-vitepress">Include VitePress for documentation? … No / Yes</a>
52
+
<spanclass="check">✔</span> <ahref="#include-vp-raw">Include support for vp-raw in VitePress? … No / Yes</a>
51
53
<spanclass="check">✔</span> <ahref="#include-github-pages">Include GitHub Pages config for documentation? … No / Yes</a>
52
54
<spanclass="check">✔</span> <ahref="#include-playground">Include playground application for development? … No / Yes</a>
53
55
<spanclass="check">✔</span> <ahref="#include-github-ci">Include GitHub CI configuration? … No / Yes</a>
@@ -140,6 +142,12 @@ For example, this project has its repository at `https://github.com/skirtles-cod
140
142
141
143
While answering this question is optional, it can be especially useful if you intend to use GitHub Pages to host your documentation, as the generated configuration files will be much closer to their final form.
142
144
145
+
## Include Tailwind CSS?{#include-tailwind-css}
146
+
147
+
[Tailwind CSS](https://tailwindcss.com/) is a popular CSS framework.
148
+
149
+
Selecting this option will add version 4 of Tailwind CSS to the project. This will include Vite configuration for all packages, as well as using Tailwind in the example code.
150
+
143
151
## Include ESLint?
144
152
145
153
Include configuration for ESLint. This will be very similar to the default configuration generated by the official [`create-vue`](https://github.com/vuejs/create-vue) tool.
@@ -172,9 +180,27 @@ Very small libraries might prefer to just use a GitHub `README.md` instead. Larg
172
180
173
181
VitePress will be configured with an `alias` to allow you to access your library within the documentation. This will use the library source code directly, without needing a build or release of the library.
174
182
183
+
## Include support for vp-raw in VitePress?{#include-vp-raw}
184
+
185
+
:::info NOTE
186
+
You'll only see this question if you chose to include VitePress *and* you're using the `--extended` flag.
187
+
:::
188
+
189
+
The default theme for VitePress can potentially clash with the CSS for components in your library. This is especially problematic when using Tailwind.
190
+
191
+
To mitigate this, VitePress supports the use of a `vp-raw` CSS class (or a `raw` custom container) to isolate component examples from the default VitePress styling:
192
+
193
+
-<https://vitepress.dev/guide/markdown#raw>
194
+
195
+
Isolating the styles will increase the size and complexity of the documentation CSS, so VitePress doesn't enable it by default. Instead, it must be enabled via a PostCSS plugin.
196
+
197
+
If you choose to include support for `vp-raw` then PostCSS will be added to the documentation package, along with the relevant configuration to enable style isolation.
198
+
199
+
This option will default to **Yes** if the project is using Tailwind.
200
+
175
201
## Include GitHub Pages config for documentation?{#include-github-pages}
176
202
177
-
You'll only see this question if you chose to include VitePress in the previous question.
203
+
You'll only see this question if you chose to include VitePress.
178
204
179
205
Selecting this option will generate configuration files for deploying your documentation to GitHub Pages via a GitHub Action. The workflow is configured to deploy from the `main` branch.
0 commit comments