Skip to content
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

JSXFragment / jsx-dom-expressions #1

Closed
iamjohnlong opened this issue Sep 8, 2018 · 4 comments
Closed

JSXFragment / jsx-dom-expressions #1

iamjohnlong opened this issue Sep 8, 2018 · 4 comments
Labels
bug Something isn't working

Comments

@iamjohnlong
Copy link

I'm trying to set up a codesandbox to play around with solid.

I'm getting

You gave us a visitor for the node type "JSXFragment" but it's not a valid type

https://codesandbox.io/s/rwvlplp084

Can you help get a template/sandbox working? Thanks!

@ryansolid
Copy link
Member

I've seen this error before on older versions of Babel. Pre Babel 7 JSX Fragment elements weren't supported. I haven't used codesandbox before but looking at dependencies I don't see where Babel is being imported. I suspect it is using Babel 6 or even one of the earlier versions of 7 beta. I developed this on the beta. However version 7 was released 10 days ago. It's possible 3rd party software hasn't updated to 7 yet.

If explicitly setting the babel dependencies is an option I imagine that should get past this. I probably should add this to the Readme.

@iamjohnlong
Copy link
Author

Yeah I thought it could be a babel version issue. I will stop being lazy and set it up locally and let you know if I have the same issue.

@iamjohnlong
Copy link
Author

iamjohnlong commented Sep 9, 2018

I created repo with everything working here https://github.com/iamjohnlong/webpack-solid

The only issue I have is needing to set r in the window here https://github.com/iamjohnlong/webpack-solid/blob/master/src/index.js#L4

@ryansolid
Copy link
Member

Hmm.. I haven't seen that in my projects. Maybe because there is no reference in the initial build it's being skipped by webpack but I use Webpack 4 as well. I wouldn't expect needing to set it on window. I wonder if any reference would keep it in scope. I will take a look when I have some time to see if I can puzzle why it happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants