-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
foxy should respect env variable COMPOSER for finding packages.json #5
Comments
So, the priority to define the directory of the
Currently, only 2 and 3 are available. |
For your example:
With your proposal, the NPM and Yarn can change the installation directory:
To determine the base directory, I check the same base of the env |
If I use the env {
"config": {
"foxy": {
"manager": "yarn",
"manager-install-options": "--module-folder /app/node_modules",
"manager-update-options": "--module-folder /app/node_modules"
}
}
} Is this sufficient? Or do you want an automatic research of the common base of directories between composer vendor directory and the composer file? |
I have just read the documentation of NPM, and it is indicated that a package is a folder containing a program described by a So, if I respect the env Foxy should not be required to use NPM or Yarn. Each developer must be able to use all native features and commands of NPM or Yarn independently of Composer. That's Foxy's goal. To conclude, I think it's a false good idea to uses the env |
Yes.
I think that's fine. I'd rather even think about not splitting update and install options. So you could have common options for both.
That's also true.
💯 % agreed!
I need to study npm/yarn more ... do you know if there's an ENV var like |
For NPM or Yarn, the package.json is must be in the root of your project. However, regarding the |
For composer also, at least if you want to use it as a library/extension. Just raised this, because it "tests" the available config options, will play around more & report.... |
I will add the |
The |
I can confirm it is working fine with |
Related to #3 (comment)
Besides that, it would be nice to have to possibility to define a custom
packages.json
file/path.The text was updated successfully, but these errors were encountered: