-
-
Notifications
You must be signed in to change notification settings - Fork 357
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
npx remark
stopped working
#1325
Comments
I can’t imagine something happening 4 days ago? There was a CLI release 7 days ago? |
Wait, has this ever worked? Because you always had to install npx --package remark-cli -- remark --help Perhaps |
This comment has been minimized.
This comment has been minimized.
Looking at a handful of my other remark-powered projects, they do have remark-cli installed locally as you describe, and this newer project does not. The strange thing is, everything was working fine until I updated deps last Friday. Perhaps remark-cli was a transitive dep of some deeper package that dropped it after I updated, which would explain why this didn't break here earlier. Either way, installing remark-cli (or just doing Thanks for the quick reply and apologies for the time sink! |
This comment has been minimized.
This comment has been minimized.
Hi! Thanks for reaching out! Because we treat issues as our backlog, we close issues that are questions since they don’t represent a task to be completed. See our support docs for how and where to ask questions. Thanks, |
No worries! |
As of ~4 days ago, invoking remark via
npx remark
in my pipelines seems to have stopped working. Given the timing, it may have to do with the latest releases of the remark and remark-cli packages.Initial checklist
Affected packages and versions
remark: 15.0.1, remark-cli: 12.0.1
Steps to reproduce
npx remark --help
in a terminal withnpx
in the path.Expected behavior
Should run remark CLI like normal.
Actual behavior
Runtime
Node v21.7.3
Package manager
NPM 10.5.0
OS
Linux (Ubuntu)
Build and bundle tools
N/A
The text was updated successfully, but these errors were encountered: