What's new?

I tweeted this the other day, but in case you missed it… Sage 9 is going to be using Webpack. This post does a great job at explaining why it’s awesome:

1 Like

In respect to Webpack’s arrival to Sage, I found some prep JS articles on modules, loaders and bundlers that made really good prep for the Unpacking Webpack article above. It’s quite easy to read and understand and gives a good high level overview.

JavaScript Modules: A Beginner’s Guide
JavaScript Modules Part 2: Module Bundling

3 Likes

Very excited for Sage 9! If only webpack would work for WP plugins asset bundling as well.

Not to sound impatient but I have to ask, do you have a rough estimate when we can expect Sage 9? :slight_smile:

None whatsoever, sorry!

Webpack from a far away looks awesome! But closer look tells me it’s another step curve. Especially since I finally got the hang of gulp and since I do 99.9% of my work on “shared hosting” environment (so no way to have node.js running on server)… Any resources for learning webpack that are less js centered, but more php side of things?

Hey Johnny!

Webpack is being used in conjunction with gulp. They are not mutually exclusive. Gulp is the task runner, webpack is the module loader. All webpack is doing here is allowing you to organize your javascript easier. Just like you would have a main.scss and import _variables.scss and _layout.scss and such: webpack makes is such that you can require javascript files from your main.js.

Node is not running on the server. It’s running on your development machine to compile your assets locally. After compilation they are uploaded to a target server on deploy.

1 Like

I’m guessing a lot of it hinges on the availability of Bootstrap 4 too, that’s still in alpha ATM.

Not sure if you’re aware but you can currently play around with the bleeding edge build of Sage 9 here: https://github.com/roots/sage/tree/sage-9 Probably not production-ready I’d say, but I’m sure another tester would be appreciated :slightly_smiling:

Yay. Hmmm… Since I’m now comfortable with the way main.js is organized with body-class related events firing only on related pages… Is there similar automagic in webpack that would pretty much allow dynamic organisation of js with muliple js files, just like composer does for PHP?

Yeah, I’m aware. Although I think I better wait a little and help test a more feature complete beta. Not sure I’d be of much help as an alpha tester.

everything is the same, we are just using webpack to organize the imports rather than dump everything on the global scope. Go look at some webpack and or ES6 module examples and everything will be clear.

BlueHost put out a open sources script that they used for updatin 2.5 mil of their blogs. IT checks for “breaks” also and then reverts if they happen which sounds interesting. More in the WP Tavern article.

2 Likes

Shopify as ecommerce platform + WordPress for content/blog is a great combo for a lot of companies and shops and now you can use Shopify on your wp sites: https://www.shopify.com/blog/113145925-introducing-shopify-for-wordpress

3 Likes

I just stumbled across this project which is billed as “The successor to Vagrant” and looks to be something similar to scotchbox. Made by the Vagrant Devs, it looks like some sort of LAMP dev box. I like the name…

The Otto Project

More details on Otto vs. Vagrant: https://www.ottoproject.io/intro/vagrant-successor.html

3 Likes

This is not a new project, but as of today, it is fully open source!

1 Like

Cool! Have you used it?

Not with Bedrock and Sage yet…

I have it installed on 2 different WordPress site that I support and didn’t develop and it works great!

The new embed template heirarchy setup in WP 4.5 has got me all excited:

2 Likes

Isotope v3 is out, dropping IE8 support, and adding new features / effects:

Github now has unlimited private repos for a flat monthly fee!

5 Likes

Digital Ocean has just launched Block Storage: https://www.digitalocean.com/company/blog/block-storage-more-space-to-scale. SSD-based storage from 1GB to 16TB @ $0.10/GB per month as a flat fee (no transfer/request costs etc.).

Sounds pretty interesting: highly available/redundant, scale any time (including through API) and totally independent from individual droplets.

The gotcha is that there’s limited regions available (needs to be in your droplet’s region) at launch but will roll out over time to new regions.

Also, further reading: https://www.digitalocean.com/community/tutorials/how-to-use-block-storage-on-digitalocean.

1 Like