-
Notifications
You must be signed in to change notification settings - Fork 8
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
3.0.0 #58
Comments
If anyone want to try if its faster then use this |
Some bads parts here, some todo for me for next week:
|
@nchanged Will the v4 plugin api have events for something like this:
Maybe best if it just runs its own tread all the time and uses it own watch so it dont mess with fusebox speed. Atm I notice I need to improve some parts, they are just making it hard for fusebox 😂 |
Here is a simple export function pluginTypeChecker(opts) {
return (ctx: Context) => {
ctx.ict.on('complete', props => {
// initial run
return props;
});
ctx.ict.on('rebundle_complete', props => {
// re-bundle
return props;
});
};
} |
@nchanged Just got old grid cleaned up and removed a lot New version have fewer options and more stuff it can do in the worker. printSettings(): void;
inspectAndPrint(): number;
inspectOnly(oldProgram: ts.EmitAndSemanticDiagnosticsBuilderProgram): IResults;
printOnly(errors: IResults): number;
worker_watch(pathToWatch: string): void;
worker_kill(): void;
worker_inspect(): void;
worker_PrintSettings(): void;
worker_print(): void;
worker_inspectAndPrint(): void; Im think this will be the sequenze
Or we can just run the watch in the backgound so we dont use time to call it |
Cleaned up more Todo:
|
plugin added |
Used no fusebox tsconfig if no path is set |
Todo
|
fixed basepath issues when using server (2 plugins) |
removed ref to homeDir |
released v 3.0.0 |
Will try and add faster checking by using IncrementalCompilerHost
The text was updated successfully, but these errors were encountered: