-
Notifications
You must be signed in to change notification settings - Fork 69
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
runCommand
ignores cwd
argument on versions after 3.6
#274
Labels
bug
Something isn't working
Comments
Thanks for reporting issue. It seems an issue with programmatic API not applying current root dir to the forked process. As a solution, you might pass await runCommand('dev', ['playground', '--no-fork']) |
Resolved in |
Wow THANK YOU! |
when I use
I'll try the |
@pi0 YES using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is my reproduction repository: https://github.com/mandarini/nuxi-bug
Using
"nuxi": "^3.9.1"
andrunCommand("dev", ["my-nuxt-app"])
,runCommand
ignores the name of the project (the directory), and runs the command in the root directory.I would expect this to work exactly like running:
If you run the above command, you will see that it works as expected.
If you run
you will see that it does not pick up the directory, and runs the command in the root directory, it shows the default Nuxt template, instead of "Hello from Katerina".
More info in the README of my reproduction repository.
At Nx we will be using version
3.6.5
, which is beforecitty
was introduced. Same version is used by@nxext/nuxt
plugin.I think that there's an issue with
citty
losing some arguments in this case. But maybe I am wrong.The text was updated successfully, but these errors were encountered: