extract-loader causing build to fail with .scss file

[mattclough1]

Problem

extract-loader causing build to fail when attempting to include an asset url to a .scss file

Example output:

./layout/checkout.liquid
Module build failed (from ../node_modules/@shopify/slate-tools/node_modules/extract-loader/lib/extractLoader.js):
NonErrorEmittedError: (Emitted value instead of an instance of Error) ReferenceError: require is not defined
    at runLoaders (/Users/mattclough/Repos/ng-theme/node_modules/@shopify/slate-tools/node_modules/webpack/lib/NormalModule.js:283:13)
    at /Users/mattclough/Repos/ng-theme/node_modules/loader-runner/lib/LoaderRunner.js:364:11
    at /Users/mattclough/Repos/ng-theme/node_modules/loader-runner/lib/LoaderRunner.js:230:18
    at context.callback (/Users/mattclough/Repos/ng-theme/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
 @ . sync ^\.\/layout.*\.liquid$ ./layout/checkout.liquid
 @ ../node_modules/@shopify/slate-tools/tools/webpack/static-files-glob.js
 @ multi ../node_modules/@shopify/slate-tools/tools/webpack/hot-client.js ../node_modules/@shopify/slate-tools/tools/webpack/static-files-glob.js

Replication steps

1. Run yarn start to start compilation of theme
2. Create a .scss file
3. In a liquid template, try including the stylesheet using its relative path, e.g.: {{ '../assets/styles/new-style.scss' | asset_url | stylesheet_tag }}

More Information

This may be fixed by upgrading extract-loader as noted here:
peerigon/extract-loader#2

UPDATE
Forked and upgraded extract-loader. The above error is replaced by a similar error require(...) is not a function

[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.