Provide a yarn add step for gem plugins with the relevant metadata when they get loaded #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This lets you use an NPM package which will get installed and run alongside your plugin. The way it works is, from the docs:
Let's assume you've been building an awesome plugin called, unsurprisingly,
MyAwesomePlugin
. In yourmy-awesome-plugin.gemspec
file, all you need to do isadd the
yarn-add
metadata matching the NPM package name and keeping the versionthe same as the Gem version:
With that bit of metadata, Bridgetown will know always to look for that package in
the users'
package.json
file when they load Bridgetown, and it will trigger ayarn add
command if the package and exact version number isn't present.