Ah, if you’re using
yarn start the assets are basically compiled in memory and then injected into the browsersync session running at
yarn start will continually recompile and re-inject styles and scripts into that session as you edit files which is great if you’re working and need to see changes right away and fiddle with them.
To compile styles and scripts and output them to your
dist directory (and view them without the browsersync session) run
yarn build. This will create your
dist directory and populate it with your compiled assets.
When you’re ready to deploy, run
yarn build:production to compress and version your assets. If you’re using Trellis you can set up a
build_before hook to take care of this step for you.
Does that help?