Closed Rodrigo54 closed 2 years ago
Yeah, that probably should have happened as soon as we added the ability to use the remark plugin by itself. I’d accept a PR for that!
I'm unsure about this tbh, as Gatsby needs the peer dependency to understand which version is supported.
The better long-term solution would be to move the non-gatsby specific components of this package into its own package, and have the gatsby plugin consume it. In that world, the former would make no mention of gatsby and the latter could have the properly versioned peer dependency. For now, we’ll just have to deal with letting the supported gatsby version be represented in documentation.
I am using this package in my blog made with
nextjs
framework I followed the example in readme.md and also did an additional configuration in mynext.config.mjs
filethis has worked perfectly for me ❤️ ! the problem is that this package installs the
gatsby
package unnecessarily and with the gatsby package comes several other unnecessary packages causing mynpm audit
to fire with several vulnerabilities problemsa simple solution would be to remove
peerDependencies
field inpackage.json
I'm available to make a pull request if that makes sense to any of you.