[BUG] Installing Compound via the Emulsify CLI results in missing .scss files from the component structure.

[jimz0r]

Describe the bug
Installing Compound via the Emulisyf CLI (either by name or --repository --checkout options), results in missing .scss files found in the components folder. This results in a failed build/develop process due to missing index and component files (e.g /components/00-base/base.scss or components/00-base/04-spacing).

This is likely due to the outdated system.emulsify.json found in the project root. New .scss index files and changes to structure need to be added/updated.

To Reproduce
Steps to reproduce the behavior:

1. Use emulsify init "MY_THEME" within a Drupal project to intirialize Emuslify theme build.
2. Navigate to "MY_THEME"
3. Use emulsify system install compound or emulsify system install --repository https://github.com/emulsify-ds/compound.git --checkout 2.0.0 to install the Compond system.
4. Run npm install
5. Run npm run develop or npm run build.

Expected behavior
After installing Compound via the Emuslify CLI, all files included in the repository should be present within the components stucture. This should result in a successful build/develop process.

Desktop

• OS: Ubuntu 22.04.4 LTS via Windows 11 WSL 2.0

[karldivad]

I couldn't even install it, using Node 20.13.0.

Case 1:

• Command: emulsify system install compound
• Error: The system you attempted to install (compound) is invalid, as it does not contain a valid configuration file.
• Folder it creates: .emulsify/cache/systems/3413609028970bcf92addcb6ca03f1f2
• After debugging, it was looking for another folder name for some reason.

Case 2:

• Command: emulsify system install --repository https://github.com/emulsify-ds/compound.git --checkout 2.0.1
• Error: Unable to install system assets and/or required components: Error: ENOENT: no such file or directory, lstat '/Users/userName/.emulsify/cache/systems/34f2b669308d477ac9688a3c9b07daed/compound/components/00-base/01-colors'
• Folder it creates: .emulsify/cache/systems/6e805b7c37e8565b3ddd400cf5040c6d
• After debugging, it was looking for another folder name for some reason.

[franxo]

Hi,
Same issue as @karldivad mentioned

[jimz0r]

@karldivad confirmed, getting the same issue.

[bariman]

getting the same issue as @karldivad , using Node 20.14.0. @callinmullaney do you have any updates on the issue?