If you could share any errors or log it would help anybody to help you
#Stuck medusa server `npm run dev`
silver copper
grizzled parrot
I only have this:
$ npm run dev
[email protected] dev
cross-env npm run build && medusa develop
[email protected] build
cross-env npm run clean && tsc -p tsconfig.json
[email protected] clean
cross-env ./node_modules/.bin/rimraf dist
silver copper
Humm nothing else at all?
grizzled parrot
cross-env ./node_modules/.bin/rimraf dist
^CError: Command failed: "C:\Users\me\workspace\------\my-store\node_modules\@babel\cli\bin\babel.js" src -d dist --ignore "src/admin/**"
at checkExecSyncError (node:child_process:890:11)
at execSync (node:child_process:962:15)
at C:\Users\me\workspace\------\my-store\node_modules\@medusajs\medusa\dist\commands\develop.js:120:42
at step (C:\Users\me\workspace\------\my-store\node_modules\@medusajs\medusa\dist\commands\develop.js:44:23)
at Object.next (C:\Users\me\workspace\------\my-store\node_modules\@medusajs\medusa\dist\commands\develop.js:25:53)
at C:\Users\me\workspace\------\my-store\node_modules\@medusajs\medusa\dist\commands\develop.js:19:71
at new Promise (<anonymous>)
at __awaiter (C:\Users\me\workspace\------\my-store\node_modules\@medusajs\medusa\dist\commands\develop.js:15:12)
at default_1 (C:\Users\me\workspace\------\my-store\node_modules\@medusajs\medusa\dist\commands\develop.js:93:12) {
status: 3221225786,
signal: null,
output: [ null, null, null ],
pid: 19320,
stdout: null,
stderr: null
}```i don't know if this helps, after ctrl-c
the server and admin where running perfectly an hour ago, I wanted to create a new store in a different folder to see if there are any changes, couldn't run the new store in dev mode, and now my old store is not running too
grizzled parrot
Also, this is an error that I received during create-medusa-app
An error occurred while setting up your project: Error: EBUSY: resource
busy or locked, unlink 'C:\Users\me\workspace\the.folder\@project\my-store\.git\objects\pack\tmp_pack_XdwYF7'
It started working after doing npm run seed
But still wondering why I got the previous behavior even in my old store that had was seeded
warped cosmos
I had this same issue for months so i stopped using "yarn dev" n started using "yarn start" so i cn make progress but now still it doesn't allow dev.
unborn kite
