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

error while installing #292

Open
vanderleisp opened this issue Dec 3, 2024 · 4 comments
Open

error while installing #292

vanderleisp opened this issue Dec 3, 2024 · 4 comments

Comments

@vanderleisp
Copy link

I´ve tried several ways to install PGLITE, but even forcing its install on backend folder then getting back to the main folder, and running "quick" I´ve always get error, like the below, on a Windows 11 machine.
Did pnpm install @electric-sql/pglite on the backend folder, and seems it installed, but then again trying to run the quick command and got the same error.

===============

$ pnpm quick

@cellajs/[email protected] quick C:\Temp\cellaJS\cella
pnpm --filter backend run quick & turbo dev --filter frontend --filter tus

[email protected] quick C:\Temp\cellaJS\cella\backend
PGLITE=true tsx scripts/quick.ts && PGLITE=true pnpm dev

'PGLITE' is not recognized as an internal or external command,
operable program or batch file.
C:\Temp\cellaJS\cella\backend:
 ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  [email protected] quick: PGLITE=true tsx scripts/quick.ts && PGLITE=true pnpm dev
Exit status 1
turbo 2.3.3

• Packages in scope: frontend, tus
• Running dev in 2 packages
• Remote caching disabled
frontend:dev: cache bypass, force executing 3098315129c9ec0b
tus:dev: cache bypass, force executing 7536d977a98805bf
tus:dev:
tus:dev: > [email protected] dev C:\Temp\cellaJS\cella\tus
tus:dev: > NODE_ENV=development tsup --watch --onSuccess "tsx dist/index.js"
tus:dev:
tus:dev: 'NODE_ENV' is not recognized as an internal or external command,
tus:dev: operable program or batch file.
tus:dev:  ELIFECYCLE  Command failed with exit code 1.
frontend:dev:
frontend:dev: > [email protected] dev C:\Temp\cellaJS\cella\frontend
frontend:dev: > NODE_ENV=development vite --mode development && node --trace-warnings
frontend:dev:
frontend:dev: 'NODE_ENV' is not recognized as an internal or external command,
frontend:dev: operable program or batch file.
frontend:dev:  ELIFECYCLE  Command failed with exit code 1.
tus:dev: ERROR: command finished with error: command (C:\Temp\cellaJS\cella\tus) C:\Users\xxxxx\AppData\Local\pnpm\pnpm.exe run dev exited (1)
tus#dev: command (C:\Temp\cellaJS\cella\tus) C:\Users\xxxxx\AppData\Local\pnpm\pnpm.exe run dev exited (1)

Tasks: 0 successful, 2 total
Cached: 0 cached, 2 total
Time: 2.429s
Failed: tus#dev

ERROR run failed: command exited (1)
 ELIFECYCLE  Command failed with exit code 1.

@flipvh
Copy link
Contributor

flipvh commented Dec 4, 2024

Hi @vanderleisp thanks for reporting this. It seems we should use cross-env to support env variables on Windows machines. let me try to get this done

@vanderleisp
Copy link
Author

tested it again and seems its working, so will test it more later. Thanks.

@flipvh
Copy link
Contributor

flipvh commented Jan 6, 2025

Thanks, sorry for taking such a long time and thnks for testing! We have running multiple projects at once 😵 .

@flipvh
Copy link
Contributor

flipvh commented Jan 13, 2025

Hi @vanderleisp you managed to get it working again? There have been maybe many breaking changes, so you might want to restart from scratch, cella is not yet ready unfortunately. Hope to get there in a few weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants