Encounter [ ERROR ] The specified engine has not resolved when setting custom engine #517
-
I am trying to use the custom engine to highlight some of my code blocks. const { Marp } = require('@marp-team/marp-core')
const highlightLines = require('markdown-it-highlight-lines')
module.exports = (opts) => new Marp(opts).use(highlightLines) However, I am always facing this error when trying to run the marp-cli command. Marp CLI execution
/usr/local/bin/node /home/marp/.cli/marp-cli.js --engine /home/marp/.cli-action/engine.js --config-file /github/workspace/examples/en/temp-config-fgk8e87h.json -I /github/workspace/examples/en
[ ERROR ] The specified engine has not resolved.
/home/marp/.cli-action/node_modules/@actions/exec/lib/toolrunner.js:592
error = new Error(`The process '${this.toolPath}' failed with exit code ${this.processExitCode}`);
^
Error: The process '/usr/local/bin/node' failed with exit code 1
at ExecState._setResult (/home/marp/.cli-action/node_modules/@actions/exec/lib/toolrunner.js:592:25)
at ExecState.CheckComplete (/home/marp/.cli-action/node_modules/@actions/exec/lib/toolrunner.js:575:18)
at ChildProcess.<anonymous> (/home/marp/.cli-action/node_modules/@actions/exec/lib/toolrunner.js:469:27)
at ChildProcess.emit (node:events:514:28)
at maybeClose (node:internal/child_process:1091:16)
at ChildProcess._handle.onexit (node:internal/child_process:302:5)
Node.js v18.17.0 I have followed the instruction from this discussion, so I am not sure what is the part that I am missing. |
Beta Was this translation helpful? Give feedback.
Answered by
johnny12150
Jun 16, 2024
Replies: 1 comment
-
It seems to be a issue related to using the wrong environment, and has been fixed now. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
johnny12150
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems to be a issue related to using the wrong environment, and has been fixed now.