You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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 byts-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 folderesm5
. 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 version8.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
.The text was updated successfully, but these errors were encountered: