-
Notifications
You must be signed in to change notification settings - Fork 8
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
TS: Using the *** tag in runtime is not supported. #13
Comments
Should be working in v1.1.3, please try again. |
🎉 Thank you, it does! |
I've just updated everything and got the same error using v1.1.3. With v1.1.2 and v1.1.1, everything works fine. I don't use typescript. I rechecked on a blank project before posting and got the same error. |
Well, isn't hacking webpack configs fun… I'll check it out. |
While fixing loader applying to TS rule, I accidentally broke the logic for applying it to JS rule. Now it should work for both. Fixes #13.
@guandjoy ok, both should now work in v1.1.4. |
@silvenon Thank you! |
Same error raises when I run: |
Hm, I wasn't able to reproduce the error. Which versions of Gatsby and gatsby-plugin-linaria are you using? |
This would be working after #18 merged. |
@silvenon here is the small repo with two branches https://github.com/guandjoy/gatsby-linaria-test But the result is the same. Now it raises the error in both develop and build cases. |
Published in v1.2.2 🚀 |
This issue has resurfaced now that Gatsby supports Typescript out of the box. The TS check doesn't evaluate properly anymore as the internal plugin doesn't seem to add the resolvers in the same way. |
Ah, I almost forgot about it. I will follow up on this issue again this weekend. |
I fixed the TS check and got it to properly configure the loader when typescript was detected, and it still failed. The only thing that worked was to manually install and add |
GatsbyJS is now supporting typescript plugin, but.. it pushes into the after of the user plugins. As a result, the linaria plugin runs before the typescript loader is attached. If the user explicitly sets the typescript plugin above it will work, but I need to find a better way. |
I believe this is related to #9.
I have Typescript, with
[email protected]
.If I use
v1.1.1
of this plugin, everything works.If I update to
v1.1.2
I get:(in the config I have this plugin listed after the Typescript one, as instructed)
The text was updated successfully, but these errors were encountered: