-
-
Notifications
You must be signed in to change notification settings - Fork 435
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: TypeStrong/ts-loader
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v8.1.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: TypeStrong/ts-loader
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v9.0.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 4,831 files changed
- 5 contributors
Commits on Mar 28, 2021
-
run comparison tests in consistent location on Windows (#1277)
* run comparison tests in consistent location * update status badge * delete old examples * Update README.md
Configuration menu - View commit details
-
Copy full SHA for 0d6c803 - Browse repository at this point
Copy the full SHA 0d6c803View commit details
Commits on Apr 7, 2021
-
Fix 'Usage with webpack watch' code example syntax (#1280)
Co-authored-by: tniezg <tomek.niezgoda@mail.com>
Configuration menu - View commit details
-
Copy full SHA for dc99b31 - Browse repository at this point
Copy the full SHA dc99b31View commit details
Commits on Apr 15, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 8a32b04 - Browse repository at this point
Copy the full SHA 8a32b04View commit details
Commits on Apr 18, 2021
-
* 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>
Configuration menu - View commit details
-
Copy full SHA for c2d1ca2 - Browse repository at this point
Copy the full SHA c2d1ca2View commit details -
Configuration menu - View commit details
-
Copy full SHA for b6c2e77 - Browse repository at this point
Copy the full SHA b6c2e77View commit details
Commits on Apr 20, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 5e08d5d - Browse repository at this point
Copy the full SHA 5e08d5dView commit details -
Configuration menu - View commit details
-
Copy full SHA for e571290 - Browse repository at this point
Copy the full SHA e571290View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v8.1.0...v9.0.2