Naman Goel
Naman Goel
> It would be more convenient if we could automatically apply these styles within the Next.js app at build time and on dev. This should be possible by automatically injecting...
@timwehrle You don't have to ask me to fork or copy from that repo! It's open source and I've publicly shared it.
The NextJS example is also used as a sanity check to ensure the types, compiler and lint rules are working as expected. The `as const` and other types are included...
@necolas That problem should have been fixed in `alpha.3`, if you're still seeing that problem I might need your help figuring out the root cause.
The ESLint rule doesn't recognise these pseudo elements. This is a bug in our ESLint plugin. Feel free to suppress the lint error and continue using it.
Try using v0.5.0-alpha.1 to see if it has fixed your problem. (Remember to reload VSCode after you update an ESLint plugin for it to take effect)
I'm not aware of a way to offer alternate types for older versions of typescript. Unless that is possible, we will just document the dependency on Typescript v5+.
@amjadorfali We might need to iterate a bit to find the best page to document this requirement, but if you're willing to go through that process, I'm happy to review.
@amjadorfali As this is a documentation task, you should read through the documentation and propose answers to those questions yourself. > What should we write? This is easy to answer....