-
Notifications
You must be signed in to change notification settings - Fork 375
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
add omitNestedClosingTags to types #1086
Conversation
seems like this will be needed too. Tried installing vite-plufgin-solid 2.7.2 , with solid-start and it wasn't able to find omitNestedClosingTags |
Hmm it's there with 2.7.2. How are you trying to set it? import solid from "solid-start/vite";
import { defineConfig } from "vite";
export default defineConfig({
plugins: [solid({
solid: {
omitNestedClosingTags: true
}
})],
}); |
You're right, it's there under: solid({
ssr: true,
solid: {
omitNestedClosingTags
} This PR would add it to: solid({
ssr: true,
omitNestedClosingTags Turns out I'm a bit confused about the nested |
It is confusing because there is a VIte plugin Solid and a separate SolidStart plugin with a solid option that passes to the Vite Plugin Solid. This weirdness goes away in the next version. I don't know.. Do the options actually pass through. If so I guess I should merge. |
@edivados Can you check if the omitNestedClosingTags is in effect when set in the outer or inner solid: {} ? |
The inner one works since it gets added to presets in vite-plugin-solid. The outer one gets passed down to vite-plugin-solid but it does nothing with it so it does not end up in dom-expressions. |
Okay, thanks for checking it out. |
Thanks you both. Ok. I'm going to do the release now. |
Typescript is complaining about omitNestedClosingTags missing in vite config.
This PR might not be needed if solidjs/vite-plugin-solid#122 is merged.