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

Live Editing generation is slow #946

Open
tiliev opened this issue Feb 13, 2019 · 3 comments
Open

Live Editing generation is slow #946

tiliev opened this issue Feb 13, 2019 · 3 comments

Comments

@tiliev
Copy link
Contributor

tiliev commented Feb 13, 2019

Description

The live editing generation (gulp generate-live-editing) is slow. It takes about a minute and a half on a fast dev machine. Please do a research and try to decrease the required time.

When tackling this issue, please consider the starting points from below.
We do transpilation of the node_modules/igniteui-angular because it is ES6. This slow us down significantly. The transpilation is done by ts-node which treats our package as typescript and transpiles it - code. Please keep in mind we have es5 version of our package inside of the folder esm5. But we'll have to change the imports in the live editing configurations which we send directly to StackBlitz. This could be worked around of course.
Also, please consider other es6 transpilers like babel. They might do it faster and use caching. ts-node does not have any caching as of version 8.0.0.
Using the ES6 package directly will be perfect, but node.js does not yet support it by default. There are some packages which enable that, like esm.

@HUSSAR-mtrela
Copy link
Collaborator

xsharp team is considering moving all our samples to static stackblitz such that we do not have to generate them from this repo. This way we could also speed up loading our controls on stackblitz. @gmurray81 do you want to add anything else?

@radomirchev
Copy link

@HUSSAR-mtrela , @gmurray81 , any update on live editing for the samples?

@radomirchev radomirchev assigned HUSSAR-mtrela and unassigned zdrawku Mar 31, 2021
@gmurray81
Copy link
Member

you mean like the same breakdown we do for WC/React @HUSSAR-mtrela ?

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

No branches or pull requests

5 participants