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
fix(terser-webpack-plugin): target webpack@5
#49314
fix(terser-webpack-plugin): target webpack@5
#49314
Conversation
CI is failing, because |
@buschtoens Thank you for submitting this PR! I see this is your first time submitting to DefinitelyTyped 👋 — I'm the local bot who will help you through the process of getting things through. This is a live comment which I will keep updated. This PR doesn't modify any tests, so it's hard to know what's being fixed, and your changes might regress in the future. Have you considered adding tests to cover the change you're making? Including tests allows this PR to be merged by yourself and the owners of this module. This can potentially save days of time for you. 1 package in this PRCode ReviewsThis PR can be merged once it's reviewed by a DT maintainer. Status
All of the items on the list are green. To merge, you need to post a comment including the string "Ready to merge" to bring in your changes. Diagnostic Information: What the bot saw about this PR{
"type": "info",
"now": "-",
"pr_number": 49314,
"author": "buschtoens",
"dangerLevel": "ScopedAndUntested",
"headCommitAbbrOid": "18fc2af",
"headCommitOid": "18fc2af119e413e81992d6d477afda03c0510e7a",
"mergeIsRequested": true,
"stalenessInDays": 0,
"lastPushDate": "2020-11-03T07:45:15.000Z",
"lastCommentDate": "2020-11-04T00:47:46.000Z",
"maintainerBlessed": false,
"reviewLink": "https://github.com/DefinitelyTyped/DefinitelyTyped/pull/49314/files",
"hasMergeConflict": false,
"authorIsOwner": false,
"isFirstContribution": true,
"popularityLevel": "Popular",
"pkgInfo": [
{
"name": "terser-webpack-plugin",
"files": [
{
"path": "types/terser-webpack-plugin/index.d.ts",
"kind": "definition"
},
{
"path": "types/terser-webpack-plugin/package.json",
"kind": "package-meta-ok"
}
],
"owners": [
"Danscho",
"peterblazejewicz"
],
"addedOwners": [],
"deletedOwners": [],
"popularityLevel": "Popular"
}
],
"hasDismissedReview": false,
"ciResult": "pass",
"lastReviewDate": "2020-11-04T00:41:10.000Z",
"firstApprovalDate": "2020-11-03T07:52:49.000Z",
"reviewersWithStaleReviews": [],
"approvalFlags": 6,
"isChangesRequested": false
} |
🔔 @Danscho @peterblazejewicz — please review this PR in the next few days. Be sure to explicitly select |
@buschtoens The CI build failed! Please review the logs for more information. Once you've pushed the fixes, the build will automatically re-run. Thanks! |
Inspecting the JavaScript source for this package found some properties that are not in the .d.ts files. terser-webpack-plugin (unpkg)was missing the following properties:
|
@Danscho Thank you for reviewing this PR! The author has pushed new commits since your last review. Could you take another look and submit a fresh review? |
👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings. Let’s review the numbers, shall we? Comparison details 📊
It looks like nothing changed too much. I won’t post performance data again unless it gets worse. |
@buschtoens Everything looks good here. Great job! I am ready to merge this PR on your behalf. If you'd like that to happen, please post a comment saying:
and I'll merge this PR almost instantly. Thanks for helping out! ❤️ (@Danscho, @peterblazejewicz: you can do this too.) |
Ready to merge. Thanks everybody! 🥰 |
I just published |
Fixes #48806
Please fill in this template.
Use a meaningful title for the pull request. Include the name of the package modified.
Test the change in your own code. (Compile and run.)
Add or edit tests to reflect the change. (Run with
npm test YOUR_PACKAGE_NAME
.)Not applicable. Tests already exist.
Follow the advice from the readme.
Avoid common mistakes.
Run
npm run lint package-name
(ortsc
if notslint.json
is present).TS 4.1 is failing, because it looks up
source-map
in the repo root and not in the package-localnode_modules
directory.Error Log
Select one of these and delete the others:
If changing an existing definition:
It actually fixes the types for that version.
All tests already exist. This is merely updating the upstream types. Tests continue to pass.
tslint.json
containing{ "extends": "dtslint/dt.json" }
. If for reason the any rule need to be disabled, disable it for that line using// tslint:disable-next-line [ruleName]
and not for whole package so that the need for disabling can be reviewed.