forked from callstack/linaria
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Rollup config does not work #2
Comments
Let me know if this is still an issue with the latest release. If it is still an issue, a failing simplified test case PR would help. |
The beta version should be stable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
The rollup plugin doesn't seem to work at all, despite being executed. This is also an issue in vanilla linaria, but there seems to be 0 progress on development/issue resolution there so I figured I'd see if you could take a look.
Basically same issue as here
If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can
yarn install
andyarn test
.https://github.com/mattoni/linaria-test
If you go to the example folder, then do an
npm install
and annpm start
, you'll get the error listed in the above issue.What is the expected behavior?
Rollup plugin should work - trying to build a nice UI library with the extracted CSS will require this plugin working
Please provide your exact Babel configuration and mention your Linaria, Node, Yarn/npm version and operating system.
Listed in repo above
The text was updated successfully, but these errors were encountered: