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

Upstream update #1

Merged
merged 16 commits into from
Apr 22, 2021
Merged

Upstream update #1

merged 16 commits into from
Apr 22, 2021

Conversation

JasonKleban
Copy link
Owner

No description provided.

appzuka and others added 16 commits February 8, 2021 16:20
* Add afterDeclarations to getCustomTransformers in README.md

* Emit d.ts file in subsequent runs in watch mode

* Update package.json and changelog.md

* Re-fixed missing errors in watch mode

* Correct merge error
Co-authored-by: John Reilly <johnny_reilly@hotmail.com>
* Optimize fileExists callback path
Instead of looking up filePathKey twice, cache in in the local scope. This isn't a hugely expensive lookup path, but is a hot path on large project recompiles (especially after caches are blown away). Profiling shows that even the Map lookup shows non-trivial cache lookup aggregate time

* Update Changelog & package.json
* Update README.md

* Update .travis.yml
* feat: remove top-level typescript import statements

* Update package.json

* Update CHANGELOG.md

Co-authored-by: John Reilly <johnny_reilly@hotmail.com>
* run comparison tests in consistent location

* update status badge

* delete old examples

* Update README.md
Co-authored-by: tniezg <tomek.niezgoda@mail.com>
* start webpack 5 migration

* fixes

* compiles now

* upgrade karma webpack

* drop webpack 4 code branches

* regenerate test output

* Stop testing TypeScript 3.6 and 3.7

* remove flaky test

* delete ignored tests

* upgrade chrome laungcher

* upgrade to 4.1.5

* implement @alexandar-akait's suggestion

* use webpack.sources.RawSource as suggested by @JonWallsten

* upgrade webpack introduce flaky test mechanism for platform

* execution tests on windows execute in c:\source\ts-loader

* ignore test failures on windows

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* Update create-and-execute-test.js

* fix test cases on windows (#1273)

* Update after-compile.ts

* Update create-and-execute-test.js

* Update CHANGELOG.md

* make node 12 the minimum version

* Update push.yml

* Update README.md

* remove 3.6 test output

* remove 3.7 test output

* remove 3.8 test output

* remove 3.9 test output

* remove 4.0 test output

* tidy

* fix

* lint should compile too

* delete unused

* remove unused

* upgrade karma

* upgrade fs-extra

* upgrade types and eslint

* remove html-webpack-plugin as unused

* update changelog

* update vanilla example

* use webpack type

* enrich WebpackLoaderContext type

* target es2018

Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
…sing compiler default functions (#1287)

* ClearCache for watchHost

* Use module resolution cache

* Use complete ResolvedModuleFull from typescript

* Use type reference directive cache so that results are atomic like module resolution till watch is invoked

* Some updates

* Test baseline update

* Update src/servicesHost.ts

* Update src/servicesHost.ts

* Update CHANGELOG.md

* Update package.json

* Update src/interfaces.ts

Co-authored-by: John Reilly <johnny_reilly@hotmail.com>
@JasonKleban JasonKleban merged commit 6d04d44 into JasonKleban:master Apr 22, 2021
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 this pull request may close these issues.