-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
[ERROR] The specified engine has not resolved. #224
Comments
You're lacking a step to install modules. As shown in the example, the custom engine has to install Marp Core package and plugins through npm package manager individually.
|
I installed both before globally. Do they need to be local? |
Right, that's unfortunate. I tried local install and it works. I was hoping to use marp-cli on multiple presentations without scattering node-modules/ directories everywhere. This (also discussed on SO) is from the npm release logs v1.0 (year 2011 :))
Obviously not up-to-date but I couldn't find anything in the latest docs.. I was hoping to do 2., would there be a way to still do this (knowingly running into version issues later)? I will try npx now.. Thank you! |
@simonmaris I found out a way to enable global modules. NODE_PATH=$(npm root -g) marp --engine @marp-team/marp-core Node.js's |
WOW, thank you, that's fantastic! May I ask one last question? 😇
I couldn't find any examples of a custom engine that extends md.renderer.rules. I saw the official plugins like math using marpitPlugin, would this be the way to go? I would be very grateful for a pointer or basic example! |
Please follow our contribuding guildeline. https://github.com/marp-team/.github/blob/master/CONTRIBUTING.md#report-issue
https://github.com/marp-team/.github/blob/master/SUPPORT.md#no_good-github-issue
|
Hi!
For some reason, I seem to be unable to define an engine for marp-cli. I was going to add custom markdown-it plugins, but have tested this minimal example to show the problem.
The same error message happens when I tried to add
--engine ./engine.js
with the following:Any ideas?
Thank you very much for building this!
The text was updated successfully, but these errors were encountered: