Subscribe
Sign in
Start new thread
Netlify
p/netlify
The composable platform for modern sites, stores, and apps.
Visit Product
Robert Fenstermacher
Netlify Build Plugins — Optimize your site & boost developer workflow at every build
Featured
21
•
Introducing Netlify Build Plugins - Get Jamstack Automation. In one-click, you can install plugins that cache files, check for broken links, trigger testing, & more—every time you deploy or build your Netlify site. You can even create your own and share it!
Replies
Hugh Durkin
Netlify Build Plugins are so easy to set up and use, you can make pancakes at the same time 👇 https://twitter.com/hughdurkin/s...
ehmicky
Maker
@hughbeme We can't automate your pancake making yet, but we'll strive to automate everything else! :)
Cassidy Williams
I ran the accessibility one on my site yesterday and I *love* that it did that work for me, so pumped about this finally being launched :)
Scott Mathson
Maker
@cassidoo that's seriously such an awesome plugin! Kudos @swyx 👏https://github.com/sw-yx/netlify... I've been quite impressed with the /sitemap.xml plugin personally: https://github.com/netlify-labs/...
Juha Liikala
All the things you guys & gals at Netlify do just keep getting more and more valuable by the day! Loving it! 😍
Kristy Marcinova
Top Product
Maker
@juhaliikala: Thank you for the kind words! 🙌
David Thyresson
Been thinking of use cases. I read through the documentation and wondered if there are any plans to include access to the logs either to parse warnings (WARN level) and then pass on to a notification/alert/email/slack or even to forward as a stream to another logging service (Papertail or the like) ... or ... is there file access to the resulting build log file that `onPostBuild` or `onEnd` could send this log file to someplace like S3?
David Thyresson
I had another use case idea this afternoon having looked at the plugin that pre/appends a deploy mode to ENV's here: https://www.netlify.com/blog/202... such that and env of DATABASE_URL and become STAGING_DATABASE_URL etc without kludgy build script logic. In some cases, an app of mine will use a third-party API service like Feedly https://feedly.com/ (to fetch and process news articles). The developer API tokens are valid for 30 days and have to be refreshed using a refresh token. The nice thing is that the refresh token won't expire, so one can reuse the refresh token to obtain a new valid API token to use with the service. So - if one refreshes the token "onPreBuild" and override the ENV, you'll always be guaranteed to have valid API token in your deployed build. And if you want to get super fancy, with build plugin scripts's caching, you could stash a small file with a timestamp of when last refreshes and only do so when approaching or 30 days' expiration. Least I think so - will try in my new app am building over weekend.
ehmicky
Maker
@dthyresson About logs: we have a feature request for just that! https://github.com/netlify/build... Feel free to subscribe to that issue to see our progress on that feature :)
Rowe Morehouse
Congrats, Netlify … you guys are getting better and better.
ehmicky
Maker
@rowemore Thanks Rowe, we're giving it our best!
Ben Church
Congrats Netlify! Youve already been a go to tool in my stack for the last 3 years. Nice to see you getting even better
Scott Mathson
Maker
@bnchrch we love feedback like this! Thanks Ben!
Markus Seyfferth
Plugins make the whole ecosystem even more valuable! They made such a difference for the WordPress world and it’s really great to hear that things like checking for broken links can be done by a plugin, too! Love that!
ehmicky
Maker
@indysigner Thanks Markus!
Eikleison Belga
Great addition to the platform. Am I allowed to offer a free plugin and charge people for more features? Something similar to wordpress plugins where people can pay to get more feature
Jessica Parsons
@tidderjail We have published guidelines for plugin authors: https://github.com/netlify/plugi... They include a link to npm's Open Source Terms (https://www.npmjs.com/policies/o...) which apply to all plugins because they must be published to npm for other users to install them. The "Commercial Content" section of those terms touch on some areas related to your question. Also, it's a totally valid use case to make a plugin that connects a person's Netlify site to another SaaS that includes a paid plan. We already have some plugins that do that. Over the coming months, we'll definitely be working on learning about these sorts of use cases, and what plugin authors and users do (and want to do) with the system. I'd be curious to learn more about what you're thinking of building, if you'd like to share.
Eikleison Belga
@jessica_parsons I haven't thought about anything yet, I asked about it because that is a market to explore now that I know that I can charge for premium features, Wordpress has thousands of plugins but netlify is starting now, so there is still thousands of things to build. Thank you for amazing answer
Robert Fenstermacher
Maker
Hello Product Hunt community! I’m excited to share the launch of Build Plugins from Netlify! This is all about automating build tasks and customizing the build process. We wanted to make your development workflow faster and your site even better. With Build Plugins you can add all sorts of clever capabilities with just a click in the Netlify UI - find any lingering bugs with Sentry, check for broken links, run an end-to-end test with Cypress and so much more. Then, when you deploy or build your Netlify site, the code will run in the background at a designated event of the build process. What’s nice about plugins is that they're just regular JavaScript objects, so the usage is fairly straightforward. You can see a full list of plugins when you sign in to Netlify https://app.netlify.com/plugins or head to our docs to learn more https://docs.netlify.com/configu...