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

babel transpiler slowness #81

Open
layik opened this issue May 12, 2020 · 1 comment
Open

babel transpiler slowness #81

layik opened this issue May 12, 2020 · 1 comment
Labels
question Further information is requested wontfix This will not be worked on

Comments

@layik
Copy link
Member

layik commented May 12, 2020

There are various issues which are rooted in transpiling (translate/compile) React. I will document those in issues for the future of the package as well.

But at the heart of this is what BabelJS does to the react code and the way "webpack" is built. I do not propose to go around this unless there are good evidence that some sort of other "bundler" such as "gulp" etc can do the job.

Just putting it out here so I can add some data and hopefully someone will offer some insight.

@layik layik added question Further information is requested wontfix This will not be worked on labels May 12, 2020
@layik layik changed the title babel transpiler issues babel transpiler slowness May 12, 2020
@layik
Copy link
Member Author

layik commented May 12, 2020

Experimental solution to this is what gp_map uses. This is a one file BabelJS and react, this was not the way geoplumber was hoped to be used.

An R powered React frontend application that is kick started by geoplumber R package but continue to grow with or without traces of geoplumber R package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant