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

[js] Update all npm dependencies (2020-12-17) #57

Merged
merged 1 commit into from
Dec 17, 2020

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Nov 30, 2020

This is your weekly update of all npm dependencies. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @rollup/plugin-node-resolve (10.0.0 → 11.0.1, major) · Repo

✳️ autoprefixer (9.8.6 → 10.1.0, major) · Repo · Changelog · Release · Diff

✳️ postcss (7.0.35 → 8.2.1, major) · Repo · Changelog · Release · Diff

✳️ postcss-at-rules-variables (0.1.10 → 0.2.1, major) · Repo · Changelog · Release · Diff

✳️ postcss-mixins (6.2.3 → 7.0.1, major) · Repo · Changelog · Diff

✳️ postcss-nested (4.2.3 → 5.0.3, major) · Repo · Changelog · Diff

✳️ eslint (7.13.0 → 7.15.0, minor) · Repo · Changelog · Release · Diff

✳️ rollup (2.33.1 → 2.35.1, minor) · Repo · Changelog · Release · Diff

✳️ stylelint (13.7.2 → 13.8.0, minor) · Repo · Changelog · Release · Diff


Depfu Status

Depfu will only send you the next scheduled PR once you merge or close this one.

All Depfu comment commands
@​depfu refresh
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu depfu bot added the depfu label Nov 30, 2020
package-lock.json Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
@depfu depfu bot force-pushed the depfu/batch_all/npm/2020-11-30 branch from b0d94b7 to 46c35f1 Compare December 17, 2020 11:14
@depfu depfu bot changed the title [js] Update all npm dependencies (2020-11-30) [js] Update all npm dependencies (2020-12-17) Dec 17, 2020
package-lock.json Outdated Show resolved Hide resolved
@depfu depfu bot force-pushed the depfu/batch_all/npm/2020-11-30 branch from 46c35f1 to f8d8a32 Compare December 17, 2020 17:28
@AlexWayfer AlexWayfer merged commit 6679866 into master Dec 17, 2020
@AlexWayfer AlexWayfer deleted the depfu/batch_all/npm/2020-11-30 branch December 17, 2020 23:20
@AlexWayfer
Copy link
Owner

@halfbyte just as post-note: I've pulled and ran npm install, here is the diff:

diff --git a/package-lock.json b/package-lock.json
index 555329c..c392d62 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -9,18 +9,18 @@
 				"date-fns": "^2.16.1"
 			},
 			"devDependencies": {
-				"@rollup/plugin-node-resolve": "11.0.1",
-				"autoprefixer": "10.1.0",
-				"eslint": "7.15.0",
-				"postcss": "8.2.1",
-				"postcss-at-rules-variables": "0.2.1",
-				"postcss-mixins": "7.0.1",
-				"postcss-nested": "5.0.3",
+				"@rollup/plugin-node-resolve": "^11.0.1",
+				"autoprefixer": "^10.1.0",
+				"eslint": "^7.15.0",
+				"postcss": "^8.2.1",
+				"postcss-at-rules-variables": "^0.2.1",
+				"postcss-mixins": "^7.0.1",
+				"postcss-nested": "^5.0.3",
 				"remark-cli": "^9.0.0",
 				"remark-gfm": "^1.0.0",
 				"remark-preset-lint-recommended": "^5.0.0",
-				"rollup": "2.35.1",
-				"stylelint": "13.8.0",
+				"rollup": "^2.35.1",
+				"stylelint": "^13.8.0",
 				"stylelint-config-standard": "^20.0.0",
 				"stylelint-no-unsupported-browser-features": "^4.1.4",
 				"yaml": "^1.10.0"

Seems not critical, but…

@halfbyte
Copy link

halfbyte commented Dec 18, 2020

@halfbyte just as post-note: I've pulled and ran npm install, here is the diff:

Seems not critical, but…

Huh, that's weird - Let me do some more tests on our side - What version of npm are you using locally (just so we can eliminate that as a cause?)

EDIT: Found a possible reason for this. Thanks for reporting this back. Unfortunately, solving this is going to be a bit more complicated, so I won't be able to do a fix today - hopefully I'll get to it next week so we can get you a fix before the xmas break.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants