This website requires JavaScript.
Explore
Help
Sign in
foster
/
denoland-deno
Watch
1
Star
0
Fork
You've already forked denoland-deno
0
mirror of
https://github.com/denoland/deno.git
synced
2024-11-15 16:43:44 -05:00
Code
Issues
Wiki
Activity
0163cedd80
denoland-deno
/
cli
/
tests
/
single_compile_with_reload.ts
5 lines
142 B
TypeScript
Raw
Normal View
History
Unescape
Escape
Incremental compilation for TypeScript (#6428) This commit adds incremental compilation capabilities to internal TS compiler. Instead of using "ts.createProgram()" API for compilation step (during deno startup), "ts.createIncrementalProgram()" API is used instead. Thanks to TS' ".tsbuildinfo" file that already stores all necessary metadata for compilation I was able to remove our own invention that is ".graph" file. ".tsbuildinfo" file is stored alongside compiled source and is used to cache-bust outdated dependencies, facilitated by the "version" field. The value for "version" field is computed in Rust during loading of module graph and is basically a hash of the file contents. Please keep in mind that incremental compilation is only used for initial compilation (or dynamic imports compilation) - bundling and runtime compiler APIs haven't been changed at all. Due to problems with source map I changed compilation settings to inline source map (inlineSourceMap instead of sourceMap).
2020-06-24 10:59:12 -04:00
await
import
(
"./single_compile_with_reload_dyn.ts"
)
;
fix: several regressions in TS compiler (#6177) This commit fixes several regressions in TS compiler: * double compilation of same module during same process run * compilation of JavaScript entry point with non-JS imports * unexpected skip of emit during compilation Additional checks were added to ensure "allowJs" setting is used in TS compiler if JavaScript has non-JS dependencies.
2020-06-10 10:02:41 -04:00
console
.
log
(
"1"
)
;
Incremental compilation for TypeScript (#6428) This commit adds incremental compilation capabilities to internal TS compiler. Instead of using "ts.createProgram()" API for compilation step (during deno startup), "ts.createIncrementalProgram()" API is used instead. Thanks to TS' ".tsbuildinfo" file that already stores all necessary metadata for compilation I was able to remove our own invention that is ".graph" file. ".tsbuildinfo" file is stored alongside compiled source and is used to cache-bust outdated dependencies, facilitated by the "version" field. The value for "version" field is computed in Rust during loading of module graph and is basically a hash of the file contents. Please keep in mind that incremental compilation is only used for initial compilation (or dynamic imports compilation) - bundling and runtime compiler APIs haven't been changed at all. Due to problems with source map I changed compilation settings to inline source map (inlineSourceMap instead of sourceMap).
2020-06-24 10:59:12 -04:00
await
import
(
"./single_compile_with_reload_dyn.ts"
)
;
fix: several regressions in TS compiler (#6177) This commit fixes several regressions in TS compiler: * double compilation of same module during same process run * compilation of JavaScript entry point with non-JS imports * unexpected skip of emit during compilation Additional checks were added to ensure "allowJs" setting is used in TS compiler if JavaScript has non-JS dependencies.
2020-06-10 10:02:41 -04:00
console
.
log
(
"2"
)
;
Copy permalink