Continued Support for Slate?
s10wen opened this issue Β· 9 comments
With this project no longer being supported by Shopify:
This repo is no longer active. See README for details
https://github.com/Shopify/slate#-slate---end-of-support-january-2020
I'm wondering out of all the forks:
https://github.com/Shopify/slate/network/members
Is anyone actively continuing to work on Slate?
I'd love to see further development and help out where I can until Shopify release their improved solution.
@s10wen, at my organization we completely removed slate and implemented themekit and webpack which allowed for a bit more control. This has allowed us to get a better understanding of the tooling and allowed us to upgrade the dependencies referenced in slate. https://github.com/hayes0724/shopify-webpack-themekit offers some good direction as well as https://github.com/the-couch/slater.
@alotoftype cheers, I'll check this out!
Why would they not support something they put out. Very concerning indeed
https://github.com/Shopify/slate#-slate---end-of-support-january-2020 => "Slate was built upon Theme Kit". Looks like they want to concentrate on improving other areas first, such as the API and the 'Sections architecture' first: https://shopify.dev/tutorials/develop-theme-get-started-with-sections-architecture
Hopefully when they are developed a bit further, they'll pick it back up, or create something else more suitable for the new setup π€π»
I continue to use Slate and fix some bugs on my fork https://github.com/ChacunSonSite/slate I need dedicate some time to update the documentation for include the upgrades I do like full support for windows. I open to contributions and ideas
@chefjuanpi What changes have you added so far? I'd ideally like to work with Slate since it's the best tool (IMO) for building Shopify Themes, without having to resort to a headless option.
- Full support for windows.
- Add webpack-bundle-analyzer, just use
yarn build --analyze
oryarn build -a
. it helps to catch where the build can be optimized. - Remove Slate-analytics (it's dead no one is reading this...)
- upgrade packages and rewrite the call when is necessary.
I'm block upgrading htmlWebpackPlugin the template is uncompatible, with the new version. I like to upgrade this for use better optimizations during buils. Now it's possible to use webpack optimization on slate.config.js something like:
if (process.env.NODE_ENV === 'production') {
optimization = {
splitChunks: {
chunks: 'all',
automaticNameDelimiter: '-',
name: true,
cacheGroups: {},
minSize: 100000,
maxSize: 200000,
},
mergeDuplicateChunks: true,
};
}
it split the bundle into chunks (better for accelerating the time response and charge) but /snippets/script-tags.liquid
and /snippets/style-tags.liquid
only list the chunks, you need to manually insert the liquid code to optimize and organize the Js and css calls.
- Full support for windows.
- Add webpack-bundle-analyzer, just use
yarn build --analyze
oryarn build -a
. it helps to catch where the build can be optimized.- Remove Slate-analytics (it's dead no one is reading this...)
- upgrade packages and rewrite the call when is necessary.
I'm block upgrading htmlWebpackPlugin the template is uncompatible, with the new version. I like to upgrade this for use better optimizations during buils. Now it's possible to use webpack optimization on slate.config.js something like:
if (process.env.NODE_ENV === 'production') { optimization = { splitChunks: { chunks: 'all', automaticNameDelimiter: '-', name: true, cacheGroups: {}, minSize: 100000, maxSize: 200000, }, mergeDuplicateChunks: true, }; }
it split the bundle into chunks (better for accelerating the time response and charge) but
/snippets/script-tags.liquid
and/snippets/style-tags.liquid
only list the chunks, you need to manually insert the liquid code to optimize and organize the Js and css calls.
That sounds great! Thank you π. I'll take a look at it and try it out. Leaning more towards this than setting up a custom webpack configuration, using another tool, or even going headless. I've been working with slate since the early beta and would much rather stick to what I know best.
If you put together a roadmap, I wouldn't mind making some contributions in my free time.