-
Notifications
You must be signed in to change notification settings - Fork 629
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
Not possible to build on Windows #440
Comments
Hi, I got an error on IE11 because of the following lines in Thumbs.js, where shorthand property names (ES2015) are used (not supported in IE11):
|
@ludem I think that's more related to #439 ! And if configuring babelrc to allow IE11 it should work as well with this. But I'm waiting for a response from @leandrowd to see if IE11 should be supported before making a PR |
@erikarenhill You're right, I meant to comment the other thread! |
gh-440: Remove env vars to allow building on windows without issues
I've removed the env var so please pull and check if you can build the new version on windows. |
I tried it but the output is just "Successfully compiled 0 files with Babel." meanwhile the output from my PR is showing 6 files. Will try and find why later today (running yarn run lib:build-es) The style compilation does not run on Windows either due to |
If it can help, my issue is totally resolved by the 3.2.7. |
@leandrowd For babel to work on windows, the .ts,.tsx seems to have to be specified without the single quotes around them: babel/babel#9803 (comment) I tested this and after removing the single quotes it compiles. Also still must replace mkdir for mkdirp or similiar solution to have it working to build the styles in Windows. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Currently it's not possible to build the project on Windows.
Adding a PR (#441) with a suggested solution using cross-env and babel parameter --extension '.ts'
The text was updated successfully, but these errors were encountered: