search

Ladvace / astro-bento-portfolio

Astro-bento-portfolio is a minimal bento-like (almost) single page portfolio website made in Astro
https://sparkly-speculoos-0c9197.netlify.app/
MIT License
176 stars 63 forks source link

Unable to Run Project Locally #8

Closed shahilpravind closed 3 months ago

shahilpravind commented 3 months ago

Hi, template looks great however, I am unable to run it on my local machine. Tested on two different machines (one with Windows 10, another 11) to the same result).

I git cloned the template, ran npm install, then npm run dev which leads to the following error.

> astro-bento-portfolio@0.0.2 dev
> astro dev

02:13:26 [WARN] [config] The feature "assets" is experimental and subject to change (used by @astrojs/netlify).

 astro  v4.9.2 ready in 1697 ms

┃ Local    http://localhost:4321/
┃ Network  use --host to expose

02:13:27 watching for file changes...
02:13:27 [ERROR] [UnhandledRejection] Astro detected an unhandled rejection. Here's the stack trace:
Error: EMFILE: too many open files, open 'D:\...\astro-bento-portfolio\node_modules\zod-to-json-schema\dist\types\parsers\readonly.d.ts'
  Hint:
    Make sure your promises all have an `await` or a `.catch()` handler.
  Error reference:
    https://docs.astro.build/en/reference/errors/unhandled-rejection/
  Stack trace:
    at process.handleUnhandledRejection (file:///D:/.../astro-bento-portfolio/node_modules/astro/dist/vite-plugin-astro-server/plugin.js:43:23)
    at emit (node:internal/process/promises:149:20)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)

Any assistance would be appreciated.

Ladvace commented 3 months ago

Hi, can you tell me what OS you are using? I'm not really able to reproduce it so at the moment it's kinda difficult to fix it

shahilpravind commented 3 months ago

Tested on 2 machines, one with Windows 11 Pro and another with Windows 10 Home.

shahilpravind commented 3 months ago

I just tried it with pnpm and it worked.

Tested it with npm again and same issue. I think it maybe an npmrelated issue, at least on my end.

Ladvace commented 3 months ago

I'll try to figure out the problem with npm, for now I'm just gonna close the issue since it seems working at least with npm