Skip to content
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

invoke cross-env with node_modules path #210

Closed
geraldodev opened this issue May 28, 2022 · 3 comments
Closed

invoke cross-env with node_modules path #210

geraldodev opened this issue May 28, 2022 · 3 comments
Labels

Comments

@geraldodev
Copy link

geraldodev commented May 28, 2022

Hi,

Thank you for this project. I've used as a basis for changing my setup to use tailwind. I'm using ubuntu.

I had to add the path of node_modules in order to cross-env to be invoked successfully.

 "postcss:build": "node node_modules/cross-env/src/bin/cross-env.js TAILWIND_MODE=build postcss css/tailwind.css -o ./resources/public/css/app.css --verbose",

Maybe it's because you install cross-env as dependency instead of devDependencies which I think is more right.

@jacekschae
Copy link
Owner

jacekschae commented May 29, 2022

Thanks for reporting this.

Did you maybe try with installing via devDependencies? Was the result different?

@geraldodev
Copy link
Author

I gave up on using cross-env, I'm invoking two separate processes, one for shadow and one for tailwind. What I'm experiencing with tailwint is the slowness over time until the point of locking. I think its because of tailwindlabs/tailwindcss#7449 . It took a morning working until the lock up happend. At afternoon I didnt start the tailwind process , and keep using vim and shadow on the same project editing the same code, without lock up.

@stale
Copy link

stale bot commented Jul 19, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 19, 2022
@stale stale bot closed this as completed Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants