Nikhil Saraf

We also have another section where we use the solid `babel` compiler and override it with options: ```typescript async transform(code, id, transformOptions) { const isSsr = transformOptions === null ||...

This is the `transform` function from `function solidStartFileSystemRouter(options)`

@rturnq Could you review this once and see if its okay to do, and if there is anything we should consider specially? Otherwise I'll implement it as suggested

This is a fair point and we should definitely try to do something about it, I wonder how typesafe we can make it.. there are levels .. do we want...

https://vitejs.dev/guide/features.html#postcss

I think these APIs follow the pattern of our `@solidjs/meta` components, i.e they should overwrite by default, and have an API with `append: true` for appending since that's the unusual...

Do you think we can handle the `cleanup` side of this as well.. checkout the `onCleanup` function below the code you edited where we cleanup `set` headers. Could you handle...

This is a weird issue with vite codesplitting..should be fixed by https://github.com/solidjs/solid-start/commit/aae4836fbebba7315de3a2a8bc4321bad8829e29

Could you point out the specific ones so we could deal with them? Or make a PR?

@modderme123 could you make a PR for what you have! I can work on top to get it to completion for strict mode