Closed Music47ell closed 3 years ago
I actually have not tried developing it that way with npm link
. When building you might need to remove "type":"module"
from package.json. This was causing quite a bit of problem as next js does not support esm.
Thank you. That did work.
How do you develop it? Maybe your way is easier than my way.
I just test it with rehype
, but that's because I know the input and output of the unified pipeline. Might try out your method next time for a more visual development process.
Using my method, I get to see all the changes on the blog right away.
All you need to do is run npm run build
after every change you make to the plugin.
You can set the build to watch mode to automatically build on change I believe. Will try it your way the next time!
I just added --watch
to the build command and it worked. Thanks.
I'm trying to test this plugin locally but I'm getting an error.
Current Behavior
Steps to Reproduce
npm run build
npm link
npm link rehype-prism-plus
npm run dev
Context
I wanna see if I can implement a new feature to this plugin. The one inside the
mdx-bundler
branch of timlrx/tailwind-nextjs-starter-blog works fine. But as soon as I switch to the local build, I get the error.