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

The code generator has deoptimised the styling of [some file] as it exceeds the max of ”100KB“ #221

Closed
ghost opened this issue Aug 27, 2015 · 10 comments

Comments

@ghost
Copy link

ghost commented Aug 27, 2015

Any workaround for this?? It's kinda urgent.

The code generator has deoptimised the styling of [some file] as it exceeds the max of ”100KB“

@jamesplease
Copy link
Member

I've never seen this before. Which part of the boilerplate is emitting this?

Also, is it a warning or is it an error? As in, does it still build?

@jamesplease
Copy link
Member

Ref. All I did was google the error 😛

@ghost
Copy link
Author

ghost commented Aug 27, 2015

Hi. Me too googlet the error and put it to compact mode, but it still occur sometimes. And I also now get messages that Esperanto hate ES6 promises and are deprecated

Still build? Yes or no. The whole code are fucked up.

@jamesplease
Copy link
Member

Hm, interesting. I've never had an issue with Esperanto and Promises. I'm working on switching out Babel for Esperanto over here: #219.

@ghost
Copy link
Author

ghost commented Aug 27, 2015

All issues I got happend right after I exceeded 100KB. But you can also trigger a Esperanto error and Babel will not see the issue. Try import XXX form I misspelled from.
I hope you get rid of the Esperanto soon, it have been 30 minutes fight now before I found workarounds.

@jamesplease
Copy link
Member

Sorry that it's causing you frustration! I should have time to move off of Esperanto in a few days.

@ghost
Copy link
Author

ghost commented Aug 27, 2015

It's all ok. I found a workaround that works, and until you fix this I can accept too see the red warning text :)

@jamesplease
Copy link
Member

It's all ok. I found a workaround that works

Awesome! Glad to hear it!

until you fix this I can accept too see the red warning text :)

Thanks for your patience :)

Is this issue good to be closed, then?

@ghost
Copy link
Author

ghost commented Aug 27, 2015

@jmeas Yup, you can close this.

@jamesplease
Copy link
Member

Will do, then. @KFlash, I'll ping you when Esperanto has been removed from the Boilerplate!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant