We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems that if I'm using pnpm instead of npm, the inputs are no longer being loaded correctly.
I wanted to use pnpm because of how it handles link: style package dependencies for testing with local deps.
link:
The text was updated successfully, but these errors were encountered:
Do you have a repo you can share with your setup? I'd be happy to take a look
Sorry, something went wrong.
so one issue seems to be using npx within bin/local-action.js. One possible fix is using the binary path directly
npx
bin/local-action.js
const tsxPath = resolve(__dirname, '../node_modules/.bin/tsx') let command = `${tsxPath} "${path.join(packagePath, 'src', 'index.ts')}"`
Although things can get a little weird with yarn pnp, because it doesnt create node_modules by default.
Another option is detecting the current package manager and calling pnpm exec/yarn exec etc...
pnpm exec
yarn exec
ncalteen
No branches or pull requests
It seems that if I'm using pnpm instead of npm, the inputs are no longer being loaded correctly.
I wanted to use pnpm because of how it handles
link:
style package dependencies for testing with local deps.The text was updated successfully, but these errors were encountered: