#SHOPIFY MINIFY JS HOW TO#
#SHOPIFY MINIFY JS UPGRADE#

Create a Google Tag Manager accountĬlick “Create Account” to create an account with GTM.

#SHOPIFY MINIFY JS HOW TO#

Here’s how to get set up to speed up your Shopify stores: Step #1. It looks like this:īut don’t take our word for it-Airbnb increased their site’s page speed by 8% (and got a better insight into their analytics) after they used Google Tag Manager. Google Tag Manager also loads JavaScript files asynchronously so that they don’t force other elements of the page to wait for them to finish. It loads all the external scripts (tags) your Shopify theme uses in one request instead of making seventeen different HTTP requests. You can think of it as having a Shopify theme inspector. Google Tag Manager is like that, but for your Shopify store. The amount of time you spend shopping is so much lower because you only need to visit one Shopify store. You don’t have to go to the milk farm to get milk, the chicken farm to get eggs, or the farmer’s market to get vegetables anymore. IMHO these should be part of the default build process, I understand there's a reason for pushing SCSS compilation onto Shopify, but when it seriously affects the flow and speed of development, it might not be worth it.CHAPTER 1 Streamline Your Shopify Store with Google Tag Managerĭo you ever think about how convenient the supermarket is?Įverything is in one place. In my own projects I'd happily fork slate-tools to deal with these things, but I don't feel I'm the only person who would want to see SCSS compilation errors or use the latest version of Sass. So even if there was a way to override just the processCss() and processThemeJs() functions locally within the theme, that would be super handy. When you're used to working with the latest version, it's really hard to revert to a 4 year old version of the same toolįrom what I've read on this repo and the Slate repo, most people are looking to do some variation of the above, but rarely want to modify anything else within Slate tools.

Shopify's Sass is so old it doesn't support things like &_elem, let alone any of the other new features that have been added since 2013. I could be wrong but it doesn't seem possible to see compilation errors even within the Shopify console, which makes it really hard to pinpoint errors (which I encountered due to the next point)

Receive SCSS compilation errors in real-time.

For example, these are the things I want to do: I feel that most people are only going to want to change the css and js tasks. This isn't my decision, so for this project I have to stay on the safe side and use Slate as-is. They want to stay on the edge and keep Slate up to date when new features are released, but a forked slate-tools could make it harder for them to upgrade.

#SHOPIFY MINIFY JS UPGRADE#

Wednesday at 11:12 Personally I'm fine with forking slate-tools, but I work with a lot of different teams on different projects and one of them has expressed concerns about the friction a forked version of slate-tools would add to the upgrade process. If you don't plan on setting up CI testing in your own repo, you could have those same prepublish commands run at a different time - like hooked into your package's version scripts or part of your git commit flow. I had to manually build using npm run prepublish before pushing to That command is run automatically in our own repo with the Circle CI integration. However, being able to have more control over what Slate does at different stages of the build process is something that is being requested - so this falls under that category.

So at this time, what you're proposing isn't something we'd introduce to the Slate build process. And explaining the workflow wasn't something we were going to go all in on and publicly document as 'the new way themes at Shopify work'. Having both files would indeed be useful to developers who could intuit why there was both a *.js and *.min.js, but it risked being confusing for anyone else. js file, then minify it in a separate process, then replace the existing min.js with this new file isn't something we wanted to introduce as a new practice in themes. Uploading both a *.js and *.min.js file in the theme assets was debated, but ultimately we decided not to do it as we weren't convinced it was a workflow to encourage. This is something we've discussed on the Themes team as well. However, in most cases, I strongly feel like the original, un-minified JavaScript file should be preserved for merchant's developers.

Shopify minify js