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

File Loading, Processing, transforming, and transpiling #104

Open
EntraptaJ opened this issue Feb 6, 2021 · 1 comment · May be fixed by #107
Open

File Loading, Processing, transforming, and transpiling #104

EntraptaJ opened this issue Feb 6, 2021 · 1 comment · May be fixed by #107
Assignees

Comments

@EntraptaJ
Copy link
Member

I need to completly rewrite the entire module map/tree creation/discovery, and also redo how we read the files, and determine the most performant method of applying my manual transforms, potenially try to fix up the files with TypeScript transformers instead of Regex replaces, unless Regexp turns out to be more performant. I'd like to investigate the possiblilty of moving to a Redis based que and cache for the workers and the module map as a whole.

I need to do an indepth analyis and inspection to determine the most memory and CPU hungry actions and move as much as I can to an outside of script cache without sacrificing performance.

This was referenced Feb 6, 2021
@EntraptaJ EntraptaJ self-assigned this Feb 6, 2021
@EntraptaJ
Copy link
Member Author

I have "phase 1" working, which is utilizing a few workers along with BullMQ to receive specifiers and filePaths and feed them to a TypeScript program and compilerHost to determine the imported modules without doing a full transpile

@EntraptaJ EntraptaJ linked a pull request Feb 26, 2021 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant