-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
generate mode passthrough #1252
Comments
How about using |
I've experimented with |
Yes |
@jff1625 Hi! To make it works fine, I recommend to use |
Also, we can implement |
This aligns with my observation.
I prefer not to migrate the project to a different build tool at this time because (1) esbuild is otherwise a good fit, and (2) I tried quickly migrating it to bun but it was not so trivial.
I saw the similarly named issue Support glob patterns in typia generate #1251 but I'm not sure it's the same use-case. I want it to behave something like this:
The question is - would that actually be any faster? thanks! |
So I added some cache feature to |
I'm not sure if this is practical, but I think it'd be nice to be able to filter the scope of files that
tyipa generate
will process, and doing a simple file copy on any that don't match.We're unable to patch our ts compiler.
The
typia generate
step is now the slowest part of our build.Esbuild processes the output from
typia generate
.All of our typia functionality is imported from a single file, ts/guards.ts
I'm thinking the
generate
task could be a lot faster if we could tell typia that it only need to process that one file, and everything else it can just copy.What do you think? Would it make a difference to build times?
The text was updated successfully, but these errors were encountered: