Ensure classes defined in Nuxt config are imported #1013
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
Resolves #1011
β Type of change
π Description
As discussed with @ineshbose in #1011, moving to the new directory structure of Nuxt 4 causes the two
class
keys innuxt.config.ts
to no longer be caught by Tailwind. This PR puts them back using theinline()
keyword.Note that it also had to move
JSON.stringify
higher up in the code, since these need stringifying inside the keyword. This shouldn't cause any issues because the variable is private and only used once.Happy to make any changes requested!