delete linaria #36
Merged
delete linaria #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have updated our repository to work with the latest version of Next.js by attempting to integrate Linaria. Unfortunately, there is no official Next.js integration available on the Linaria repositiory at the moment: https://github.com/callstack/linaria?tab=readme-ov-file#setup
To address this, I used the package next-with-linaria, which successfully made the application compatible with the current versions of Node.js and Next.js. However, I encountered issues with the builds being unreliable. On the first run, I received the error:
Make sure you are not using a browser or Node specific API and all the variables are available in static context.On the second run, the build was successful. I suspect this inconsistency arises from an incomplete integration with Next.js's build process, leading to poor compatibility with css-variables.To ensure the pipeline remains green, I have temporarily removed the Linaria example. I am open to re-adding it if the compatibility issues are resolved in funture