summaryrefslogtreecommitdiff
path: root/cli/tests/compiler_api_test.ts
AgeCommit message (Collapse)Author
2020-09-09fix(tsc): config resolution using relative paths (#7392)Bartek Iwańczuk
2020-07-28fix: downcast from SwcDiagnosticBuffer to OpError (#6909)Bartek Iwańczuk
2020-07-14Use dprint for internal formatting (#6682)David Sherret
2020-06-18Deno.bundle supports targets < ES2017 (#6346)Ryan Dahl
This commit provides a "system_loader_es5.js" bundle loader which will be added to the bundle when the target is < ES2017, which is the minimum target syntax required for "system_loader.js". Supports #5913 (via Deno.bundle()) with a couple caveats: * Allowing "deno bundle" to take a different target is not supported, as we specifically ignore "target" when passed in a TypeScript config file. This is because deno bundle is really intended to generate bundles that work in Deno. It is an unintentional side effect that some bundles are loadable in browsers. * While a target of "es3" will be accepted, the module loader will still only be compatible with ES5 or later. Realistically no one should be expecting bundles generated by Deno to be used on IE8 and prior, and there is just too much "baggage" to support that at this point. This is a minor variation of 75bb9d, which exposed some sort of internal V8 bug. Ref #6358 This is 100% authored by Kitson Kelly. Github might change the author when landing so I'm leaving this in: Co-authored-by: Kitson Kelly <me@kitsonkelly.com>
2020-06-17Revert "Deno.bundle supports targets < ES2017. (#6328)" (#6342)Bartek Iwańczuk
This reverts commit 75bb9dbdfc7f8b4e8d17978808ae575e61843aef.
2020-06-17Deno.bundle supports targets < ES2017. (#6328)Kitson Kelly
This commit provides a "system_loader_es5.js" bundle loader which will be added to the bundle when the target is < ES2017, which is the minimum target syntax required for "system_loader.js". Supports #5913 (via Deno.bundle()) with a couple caveats: * Allowing "deno bundle" to take a different target is not supported, as we specifically ignore "target" when passed in a TypeScript config file. This is because deno bundle is really intended to generate bundles that work in Deno. It is an unintentional side effect that some bundles are loadable in browsers. * While a target of "es3" will be accepted, the module loader will still only be compatible with ES5 or later. Realistically no one should be expecting bundles generated by Deno to be used on IE8 and prior, and there is just too much "baggage" to support that at this point.
2020-06-12refactor: Don't destructure the Deno namespace (#6268)Nayeem Rahman
2020-04-28BREAKING: remove overload of Deno.test() (#4951)Bartek Iwańczuk
This commit removes overload of Deno.test() that accepted named function.
2020-03-28Update to Prettier 2 and use ES Private Fields (#4498)Kitson Kelly
2020-03-11move compiler API tests to integration tests (#4319)Bartek Iwańczuk