This repository was archived by the owner on May 10, 2021. It is now read-only.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hMmmMm. i think we should maybe hold off on this because the build plugin isn't supposed to be an alternative, it's meant to be the final iteration. at whatever point we start directing NoN users to the plugin, it should be a proactive push/suggestion to use the plugin instead of NoN and not a 'you can use this if you don't want to do extra steps'. it also at this moment has additional features over NoN (like custom netlify functions). but also it's not a big deal. would still be good to get it on people's radars. if you decide to merge the blurb as is, i'd put it under
### npm Package
for now.