Closed chrisahardie closed 3 years ago
this issue is similar to my issue, my deduction is the equal sign (=) fail the command
here is how I test it
"test":"cross-env-shell \"echo testing\""
print out testing
"test":"cross-env-shell \"echo 123\""
print out 123
"test":"cross-env-shell \"echo testing=123\""
print nothing
cross-env
7.0.2:node
version: 12.6.1npm
(oryarn
) version: 6.13.4Relevant code or config
What you did:
I have created a working
build:prod
script that reads in a environment file.I then attempted to break my
build:prod
up so that I could create adynamicBuild
script that I could use when building for different environments.What happened:
When I execute
dynamicBuild:prod
I get very little output:I have identified the issue as the
dotenv_config_path
flag indynamicBuild
- if I remove it, my build will at least kick off, though obviously not with the desired env file.Since I'm not getting any feedback, is there something I can do to get some more verbose logging?
Reproduction repository:
https://github.com/chrisahardie/cross-env-repo
Problem description:
cross-env-shell
is not kicking off a build if the dotenv_config_path flag is set.Suggested solution: