Clarify how the src/assets folder works and how it's used in a theme

[t-kelly]

Problem

As described in my response in issue #407, there is a lot of logic behind what's going on the src/assets folder. Let's get some better documentation about how things are currently setup, that way people can form educated opinions about it and propose improvements!

Related: #408

[weotch]

What about adding the asset directories to Webpack resolve modules? https://webpack.js.org/configuration/resolve/#resolve-modules

[jonathanmoore]

Right now working with static JS files does feel a bit clumsy. The other thing to note about the scenario above is that it seems like you would have to name the file modernizr.js.liquid so that it uploaded with slate-tools. Otherwise yarn start will assume that the file is being served locally from /dist.

Personally I would like to have a way to work with dependancies that are completely separate from bundled files. An example of this would be using a package like lazysizes. LazySizes needs to load as soon as possible with async, so including it in theme.js would not make sense with the files being deferred (#437).

Would it be realistic to have a build process that could do the following?

• Load a file like lazysizes.js from vendor/static
• lazysizes.js includes the various required plugins
• Inject a script tag with lazysizes.js as async

[numediaweb]

any updates on this: same issue with vendor js assets

[sebbean]

been battling this all month

[t-kelly]

Assets have been simplified in #850 and the change is now available in v1.0.0-beta.12.

Docs that have also been updated:

• https://github.com/Shopify/slate/wiki/Slate-themes
• https://github.com/Shopify/slate/wiki/Template-and-layout-bundles
• https://github.com/Shopify/slate/wiki/Local-development

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.