As of now, if the cli has to perform tasks that take awhile, such as cloning the starter repo, or a system, it simply seems to hang. This task involves adding a progress indicator in order to signal to the developer that something is happening. Perhaps we can use something like this

Expected Behavior

The progress bars shown in the attached image should be a single progress bar.

Your Environment

• Operating System and version (desktop or mobile): macOS Monteray
• ZSH shell

Describe the bug
I've installed vanilla Drupal 9 and tried to set up emulsify theme:

emulsify init "Diffy Theme"
cd web/themes/custom/diffy_theme
emulsify system install compound
npm run build

When tried to enable the theme got an error:

NOTICE: PHP message: Drupal\Core\Extension\InfoParserException: The 'core_version_requirement' constraint (^9 || ^10) requires the 'core' key not be set in themes/custom/diffy_theme/diffy_theme.info.yml

Also after I've fixed this error (by removing core property) I created a node and when viewed it got another error:

"PHP message: Uncaught PHP Exception Twig\Error\LoaderError: "Template "@molecules/tabs/tabs.twig" is not defined in "themes/custom/diffy_theme/templates/navigation/menu-local-tasks.html.twig" at line 14."

Please remove core from *.info.yml file and maybe ship tabs component when setting up the design system.

Thank you very much for this awesome project!

Resolving this issue involves creating an AJV-based validation step in relevant cli command handlers, so we can be confident that configuration files are structured correctly before using them within the rest of the handlers.

Since the Starter needs formatting/linting standards, we have those all defined in package.json however, once the starter is installed into a project, all of those things should be configured at the project root, not the theme. Ideally they would be removed from the starter's package.json, but not sure how to do that yet.

In a community meetup we identified that this repo is a good place for contribution/development docs, but the usage docs might be better located here: https://docs.emulsify.info/supporting-projects/emulsify-cli

Describe the bug
We may have a bug or at least a hiccup in documentation.
emulsify init "theme_name" does not seem to produce the same result as emulsify init "Theme Name" --starter https://github.com/emulsify-ds/emulsify-drupal.git --platform drupal. Passing the repo directly should get the latest tag which I would expect to be equivalent to not passing it when we auto-detect the platform. Some wires may be crossed there.

To Reproduce
Steps to reproduce the behavior:

1. Set up a new drupal site
2. `emuslify init "theme_name"
3. go to the installed theme
4. Install compound with a branch

Expected behavior
The latest tagged version of emulsify-drupal should be installed when not specifying the repo and drupal is detected.

Desktop (please complete the following information):

• OS: Ubuntu and MacOs for sure.

Additional context
This was noticed when looking for a specific component from compound that should auto install.

Describe the bug
Emulsify init command is not working properly

To Reproduce
Steps to reproduce the behavior:

1. Execute emulsify init
2. It will throw and error:

throw new Error(`Cannot add option '${option.flags}'${this._name && ` to command '${this._name}'`} due to conflicting flag '${matchingFlag}'
      ^

Error: Cannot add option '-c --checkout <commit/branch/tag>' due to conflicting flag '--checkout'

Desktop (please complete the following information):

• OS: MacOS 14.4.1
• Node: 20.13.0

Currently, if you install a named system and pass a repository, the repository is ignored. We should add help text to say "Only pass one or the other"

e.g. emulsify system install compound --repository https://github.com/emulsify-ds/compound.git --checkout 1.0.0 will appear to work, but will install the latest from main rather than 1.0.0 since the name compound is also passed. It seems to ignore the stuff that comes after it.

CLI technically only supports the Drupal starter still. You can use others, but it requires knowledge of the commands.

The title is pretty clear on this one. Utils to memoize:

• findFileInCurrentPath

This function can be used: https://ramdajs.com/docs/#memoizeWith

Node 16 will end of life in September 2023. We should test and migrate to Node 18 before then.

h/t @cruno91

Right now, we have an init hook within the init handler. This essentially enables starters to perform starter-specific tasks after a project has been initialized.

We need to create a system init hook that supports the same functionality, but it should be executed when a system for a project is selected.

Expected Behavior

When installing a component in Emulsify Drupal if the component includes a library to be attached like a JavaScript file, then the attachment should be names-spaced under the theme.

Additionally, the attachment should be defined in THEME_NAME.libraries.yml file if it is not already defined.

Current Behavior

The emulsify namespace is used and causes JavaScript functionality to fail.

Possible Solution

After adding the component, Emulsify CLI should replace emulsify with the specific theme name much like how it does it in .cli/init.js:89.

Steps to Reproduce (for bugs)

1. Add the tabs component from compound; emulsify component install tabs
2. Look into the twig file of the newly added component: @components/02-molecules/tabs/tabs.twig
3. You will see the attached library is name-spaced under emulsify not the actual theme.

Your Environment

• Version used: 1.5.0
• Browser Name and version: Google Chrome v96.0.4664.110
• Operating System and version (desktop or mobile): macOS Big Sur v11.6.1

@patrickocoffeyo can we host systems in a private GitHub repo?

Hi Emlusify team,

Is there some kind of starter instructions or starter repository which uses the cli?
I can install it run test etc. but I miss the link how to use it install my first component set.

Thanks!

Right now, we have a logging utility that allows for us to log/exit in a relatively simple way. However, we need to spice up our logs a bit, and make them look a little better.

Solving this issue involves replacing our console based utility with consola. We want to keep our current log utility, as it does some nice things like adding color to messages, but rather than using console, we should use consola.

Describe the bug
I'm trying to install the Emulsify UI Kit component library with the Emulsify CLI and I cannot.

To Reproduce
Steps to reproduce the behavior:

1. Go to the Standalone installation instructions
2. Change the following
   emulsify system install --repository https://github.com/emulsify-ds/compound.git --checkout [branch/tag/commit] to emulsify system install --repository https://github.com/emulsify-ds/emulsify-ui-kit.git --checkout main
3. Get the error Unable to install system assets and/or required components: Error: ENOENT: no such file or directory, lstat '/Users/oest/.emulsify/cache/systems/aafceee31da1cd49aa7dc52ebb708c40/compound/src/components/00-base/01-colors'

I updated system.emulsify.json using the instructions in the docs.

Any help would be appreciated. TY.

Right now, when emulsify init themeName is run, a Drupal-specific success message is logged. This is not good, because the CLI needs to support all platforms generically.

In order to resolve this issue, the following things must be completed:

• Add configuration to platform objects that allows for initialization success messages to be defined.
• Adjust the init command handler so it logs based on the instructions given by the platform.

Resolving this issue involves adding support for system variants that are defined in external repositories, meaning repositories that are not within the system's own repository.

Right now by default, when installing a system, we check out the main branch, and pin the project's system to the main branch. This is problematic because it will result in people accidentally updating their systems, so instead we should fetch the latest tag, and pin the user to that.

When running certain commands that include writing to files (init for example), fs.writeFile is taking forever to actually write. Need to look into why this is happening, and resolve.

Resolving this issue involves adding an ejection command that allows for developers to dump all of the specified system's components into the project.

• Rename the "master" branch to "main"
• Confirm automation in this repo continues to function successfully.

Hey y'all. I'm taking Emulsify out for a test drive but I'm having some issues with how to install all existing Compound components.

I've gone through the documentation and initializing a NEW theme project works like a charm. However, I've inherited an existing Drupal theme project that uses Emulsify but I don't see anywhere where it shows how to "initialize" an existing project and install all component files inside the "components" folder (it's currently empty). I've tried running 'emulsify system install compound' but I get the following error:

"ERROR No Emulsify project detected. You must run this command within an existing Emulsify project. For more information about creating Emulsify projects, run "emulsify init --help"

Hope somebody can throw me a rope here. :)

Init success message should instruct the developer to move into the theme root before attempting to select and/or install a system.

It would be great to have a flag for emulsify-cli that reported the version of the tool.

emulsify -v or emulsify --version should report the version of tool, similar to other command-line tools.

This will allow developers to quickly determine the version of emulsify-cli when they are troubleshooting, reporting bugs and contributing to the project.

We would need to:

• add the flag
• add tests for the flag (?)
• update inline help
• update documentation website

Expected Behavior

When installing Emulsify, the components' attach_library calls should use the name of the theme.

Current Behavior

All of the attach_library calls still say emulsify/whatever

Is your feature request related to a problem? Please describe.
Emulsify is moving to a base_theme structure with the 5.x release. However, we want to keep Emulsify platform agnostic so the --starter argument should be retooled to account for the new structure.

Describe the solution you'd like
The starter version should essential consist of the "whisk" theme template except for the following drupal files: https://github.com/emulsify-ds/emulsify-drupal/tree/main/whisk

• screenshot.png
• whisk.breakpoints.yml
• whisk.info.emulsify.yml
• whisk.libraries.yml
• whisk.theme
• templates/ directory
• config/install directory
• config/schema` directory

Additional context
Add any other context or screenshots about the feature request here.

Need:

There needs to be a way to specify and install a new system version after initial install. So that a project can update from v1.7.0 to v1.8.0 to get new components, for example.

Issue

Something wonky is happening when we install systems... we're choosing a version, and it's being captured in the project.emulsify.json file. But once it's installed, it doesn't seem to care about that file for subsequent CLI calls.

Steps to reproduce

• Create a drupal project composer create-project drupal/recommended-project cli-update
• Initialize a theme `emulsify init "My Theme"
• cd into the theme cd web/themes/custom/my_theme
• Install a system emulsify system install --repository https://github.com/yalesites-org/component-library-twig.git --checkout v1.7.0
• Verify you do not have access to the "accordion" component (it's not in the list when you run emulsify component list)
• Edit the theme's project.emulsify.json and change the "checkout" from v1.7.0 to v1.8.0
• Verify you still don't have access to the "accordion" component (even though it is included with v1.8.0) emulsify component list
• Delete your systems cache rm -rf ~/.emulsify/cache/systems/*
• Verify you now DO have access to the accordion component emulsify component list
• Edit the theme's project.emulsify.json and change the "checkout" from v1.8.0 back to v1.7.0
• Verify you still have access to the accordion (even though you shouldn't because you're back to v1.7.0) emulsify component list