-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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.
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
declaration of 'server.force' error #8398
Comments
You are using 3.0.0-alpha.7 which includes a breaking change (#8280). The currently deployed docs are for v2. Please use |
ok,thx |
I was under the assumption that people were using force from the CLI. @asasugar was is your use case to set force in the config? You are trying to avoid the cache from ever generating? This isn't the most efficient way if that is the case because the files would still be written to disk. |
I read the documentation of vite v2, and then used vite v3, the force statement reported an error, as @sapphi-red said, |
@asasugar What is the reason for using |
Describe the bug
Type '{ port: number; fs: { strict: true; }; hmr: true; force: true; }' cannot be assigned to type 'ServerOptions'.
Object literals can specify only known properties, and 'force' is not in type 'ServerOptions'. ts(2322)
index.d.ts(2171, 5): The required type is from the property "server", which is declared on the "UserConfig" type here
I found that the declaration of 'server.force' is under UserConfig, according to the documentation of vite, the declaration of force should be under
ServerOptions
Reproduction
https://github.com/asasugar/vite-element-plus-admin
System Info
Used Package Manager
pnpm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: