@stefanjudis @Netlify They are so much fun!
I've been experimenting with them quite a bit over the last couple of weeks. I'll write up my process soon, but until then, @Tzmanics is dropping knowledge all over the place!
🧠👉 https://www.netlify.com/blog/2020/04/30/whats-a-netlify-build-plugin-series-part-1-using-build-plugins/?utm_source=twitter&utm_medium=using-build-plugins-tzm&utm_campaign=devex
I've been experimenting with them quite a bit over the last couple of weeks. I'll write up my process soon, but until then, @Tzmanics is dropping knowledge all over the place!
🧠👉 https://www.netlify.com/blog/2020/04/30/whats-a-netlify-build-plugin-series-part-1-using-build-plugins/?utm_source=twitter&utm_medium=using-build-plugins-tzm&utm_campaign=devex
For example, I used this to enable incremental builds on one of my projects.
https://twitter.com/philhawksworth/status/1256293798969212933
https://twitter.com/philhawksworth/status/1256293798969212933
Currently having fun with @Netlify Build Plugins!
🚀 https://www.netlify.com/build/plugins-beta/?utm_source=twitter&utm_medium=cache-utils-pnh&utm_campaign=devex
Getting access to the cache between build offers some great opportunities!
🚀 https://www.netlify.com/build/plugins-beta/?utm_source=twitter&utm_medium=cache-utils-pnh&utm_campaign=devex
Getting access to the cache between build offers some great opportunities!
Kudos to @timbray for showing that he has the courage of his convictions.
https://www.tbray.org/ongoing/When/202x/2020/04/29/Leaving-Amazon
https://www.tbray.org/ongoing/When/202x/2020/04/29/Leaving-Amazon
@jamiemchale @Netlify Yeah... I had good success on Friday with incremental builds in an example site I made with @eleven_ty. Thanks to the new access to @Netlify's build cache, you can make this work nicely.
https://twitter.com/philhawksworth/status/1256293798969212933
https://twitter.com/philhawksworth/status/1256293798969212933
@richardherbert Yeah! He was one of my absolute favourites during that era. Utter legend!
@jamiemchale @Netlify I suppose that in addition to how often the content might change for each user, it depends somewhat on how many users you might need to service this way.
@jamiemchale @Netlify So, 1 role per user? Sounds like that would mean pages are unique for each user, which is a good use case for authentication/authorisation on the API which populates pages rather than unique pages. A popular pattern and what we do for http://app.netlify.com.
@csswizardry @hey_stac Preparation preparation preparation. My view of the production team getting ducks in a row for #AllDayHey this Thursday.
Usually just for those able to get to glorious Yorkshire. This year, anyone can attend!
Usually just for those able to get to glorious Yorkshire. This year, anyone can attend!
@addyosmani @eleven_ty @sebmck Yeah. I also like that it’s JavaScript all the way down. (But not necessarily all the way to the front)
@X_Qlusive @gerwitz @Netlify And in my example site, I do that here
https://github.com/philhawksworth/virtual-lolly/blob/ed1dd458112eef6902b8522544e20b30b64b27d9/plugins/track-latest/index.js#L52-L57
https://github.com/philhawksworth/virtual-lolly/blob/ed1dd458112eef6902b8522544e20b30b64b27d9/plugins/track-latest/index.js#L52-L57
@X_Qlusive @gerwitz @Netlify Exactly.
The cache utility of Netlify Build makes that action simple. The logic of when/what to cache is where things might get complex and each use case needs some thought.
Here’s the cache API:
https://github.com/netlify/build/blob/master/packages/cache-utils/README.md
The cache utility of Netlify Build makes that action simple. The logic of when/what to cache is where things might get complex and each use case needs some thought.
Here’s the cache API:
https://github.com/netlify/build/blob/master/packages/cache-utils/README.md
@BarstoolNewsN Or maybe just try a vegetable patch instead of murder and cannibalism.
@gerwitz @X_Qlusive @Netlify I’m using the @Netlify build environment for this. But you can run that locally which is what I do for development.
https://github.com/netlify/build
https://github.com/netlify/build
@X_Qlusive @gerwitz @Netlify - Builds retrieve previously cached pages and the timestamp of the previous build
- Builds only create new pages for content created after our timestamp
This is made pretty simple because of the content model on this site, and easy access to cache between builds.
- Builds only create new pages for content created after our timestamp
This is made pretty simple because of the content model on this site, and easy access to cache between builds.
@X_Qlusive @gerwitz @Netlify I’ll blog it in detail next week, but in summary:
- Content data comes from an API
- When the site builds it notes the timestamp of the most resent item
- After building, we cache all the API driven pages, and the timestamp of the latest item
...
- Content data comes from an API
- When the site builds it notes the timestamp of the most resent item
- After building, we cache all the API driven pages, and the timestamp of the latest item
...
@gerwitz @Netlify There isn’t a plugin for this, but all plugins get access to some utilities of which the build cache is one.
You can make and use plugins without publishing them. Which is what I did here. It’s part of the site’s code.
https://github.com/philhawksworth/virtual-lolly/tree/master/plugins/track-latest
I’ll write it up in a blog post.
You can make and use plugins without publishing them. Which is what I did here. It’s part of the site’s code.
https://github.com/philhawksworth/virtual-lolly/tree/master/plugins/track-latest
I’ll write it up in a blog post.
@DavidWells @Netlify I’m so enjoying the very logical access to such useful utilities which were juuuuust out of reach before Build plugins.
Imagination humming a little now.
Fun!
Imagination humming a little now.
Fun!