We noticed creating new extensions in a CLI 3.0 project that's using NPM as the package manager yields a yarn.lock. After some debugging we realized that the extensions' binary has some logic for installing dependencies. Since this is a responsibility that we've moved to the CLI 3.0, I'm adding an attribute to the configuration schema and using it to skip the installation of dependencies. Please let me know if you'd take a different approach for this one or place the attribute elsewhere in the yaml.
Related: https://github.com/Shopify/shopify-cli-planning/issues/280
We noticed creating new extensions in a CLI 3.0 project that's using NPM as the package manager yields a
yarn.lock
. After some debugging we realized that the extensions' binary has some logic for installing dependencies. Since this is a responsibility that we've moved to the CLI 3.0, I'm adding an attribute to the configuration schema and using it to skip the installation of dependencies. Please let me know if you'd take a different approach for this one or place the attribute elsewhere in the yaml.