Unexpected semicolon error in cargo-leptos
during CI build
#3706
Replies: 1 comment
-
I finally figured out what my issue was. At the top of my style/tailwind.css file, I had to replace |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have the following job in my CI pipeline:
I am getting the following error:
For some reason, I don't get this issue when building the app locally. The only thing that comes to mind as being different between my machine and the CI machine is that my machine uses
x86_64-unknown-linux-gnu
, while the CI machinex86_64-unknown-linux-musl
. I don't know why using a different target would cause issues with a token in the rust source code not being present though.Here's a full stack trace:
This portion of the cargo-leptos code seems to match this part of the stack trace:
I am at a loss as to why it's complaining about a semicolon being unexpected since the line brought up in the error seems to be using a semicolon correctly. If it's an error generated when parsing the stylesheet, the CSS at target/tmp/tailwind.css doesn't even have 5,739 lines.
Beta Was this translation helpful? Give feedback.
All reactions