Difference between pnpm run dev and pnpm run pages:dev?

[clibequilibrium]

Hi !

Thank you for this poc !

What is the difference between pnpm run pages:dev and pnpm run dev and when one uses one over another?
Thanks.

[gerhardcit]

as per the package.json

    "dev": "vite dev",
...
    "pages:dev": "wrangler pages dev --compatibility-date=2023-11-21 --proxy 5173 -- pnpm run dev",

pnpm dev just runs the basic vite dev, which is sveltekit standard dev
but to use miniflare binding, you have to run wrangler pages dev that proxies to the output of vite dev which is typically on port 5173
this way you have sveltekit live reloads (HMR) and the benefits of simulating your cloudflare backend workers functions that uses miniflare to achieve that.

[clibequilibrium]

as per the package.json

    "dev": "vite dev",
...
    "pages:dev": "wrangler pages dev --compatibility-date=2023-11-21 --proxy 5173 -- pnpm run dev",

pnpm dev just runs the basic vite dev, which is sveltekit standard dev but to use miniflare binding, you have to run wrangler pages dev that proxies to the output of vite dev which is typically on port 5173 this way you have sveltekit live reloads (HMR) and the benefits of simulating your cloudflare backend workers functions that uses miniflare to achieve that.

Hmm, for me pnpm dev worked just fine and I had KV and D1 working ? Could you please confirm that there is indeed a need for pages:dev ?

EDIT: or it's only needed if you use worker functions API ?

[gerhardcit]

Hmm, good point.. pages:dev might have been left over from previous methods.
you right. the hooks.server.ts will handle miniflare without the need for wrangler pages dev
unless you fiddle with environment variables to run against remote dbs for testing etc.