Closed AlexWayfer closed 1 year ago
Update both projects at the same time and it should work right now.
It takes time to go through the ecosystem. Wait a bit for the dust to settle :)
Nevermind, I've somehow messed up and there actually was remark-gfm
v3, not v4. My bad, sorry.
Hi! This was closed. Team: If this was fixed, please add phase/solved
. Otherwise, please add one of the no/*
labels.
No worries! :)
Initial checklist
Affected packages and versions
Something indirect, probably new versions of
remark-parse
due to logsLink to runnable example
No response
Steps to reproduce
I've received
remark-cli
andremark-gfm
(doesn't matter I guess) from Depfu.And I've noticed fails in Cirrus CI.
In this project were no fails in PRs, but they become after manual push to the
main
: https://cirrus-ci.com/task/6402074150174720?logs=lint#L12In this project are fails in PRs: https://github.com/AlexWayfer/flame-sentry_context/pull/6
I had no errors locally, so I believe it depends on
package-lock.json
(and CI cache).I've saved the old lock file: (oh, thanks GitHub, JSON files are too dangerous for you) package-lock.json.old.zip
And after
npm update
I've got the error locally, thepackage-lock.json
is here: package-lock.json.zipNode.js v20.7.0, npm v10.1.0 (there are no new versions in your issue template)
Expected behavior
No errors from indirect dependencies.
Actual behavior
There is error:
Runtime
Other (please specify in steps to reproduce)
Package manager
Other (please specify in steps to reproduce)
OS
Linux
Build and bundle tools
Other (please specify in steps to reproduce)