Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: typo in readme #83

Merged
merged 1 commit into from
Dec 18, 2023
Merged

fix: typo in readme #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ You can also modify the configuration, for example if you want to set an include

```js
import { createAppConfig } from '@nextcloud/vite-config'
import { mergeConfig } from 'vite'
import { defineConfig } from 'vite'
import path from 'node:path'

const yourOverrides = defineConfig({
Expand Down Expand Up @@ -89,4 +89,4 @@ For apps any styles can be injected in the JS by dynamically inject the styles i
But this only works in DOM environments, so for libraries this might not work (e.g. while testing in the Node environment).

So for libraries the CSS will still be extracted by Vite, but the extracted CSS assets will be imported.
This way the library user can decide how to handle the imported CSS without relying on a DOM environment.
This way the library user can decide how to handle the imported CSS without relying on a DOM environment.
Loading