Internal Server Error: esbuild_1.startService is not a function about vite-plugin-react-pages HOT 5 CLOSED

I ran yarn create vite-pages app-demo --template app, which got the latest create-vite-pages. Then npm and pnpm just fixed themselves right after, and started fetching the latest version as well. I have no clue what caused the issue or why using yarn fixed npm and pnpm. It's also a bit concerning that npm init isn't guaranteed to fetch the latest versions of templates, but at least I'm unstuck for now. Thanks for your help!

from vite-plugin-react-pages.

It is fixed in the latest version. You can try it again! You can close this issue if it is fixed.

from vite-plugin-react-pages.

On the machine that produces this issue, creating a new vite-pages project still gives me a package.json like this https://github.com/khalibloo/vite-pages-esbuild-bug/blob/master/package.json with vite-plugin-react-pages version 2.x.
Any ideas why running the npm init would give me the old version of the template? I believe the init command should always fetch the latest template, right?

from vite-plugin-react-pages.

It may be a bug of npm's cache. (By the way, are you using a custom npm regiatery? That would also cause the problem.)

Try upgrading your npm version. Or delete npm cache.
This may be helpful: https://docs.npmjs.com/cli/v7/commands/npm-exec#a-note-on-caching

from vite-plugin-react-pages.

Nope, default configs for all 3 package managers. I suspected it might have been a cache issue with npm initially, given that i've used vite-pages on the machine with the issue a long time ago. But I just installed pnpm maybe 2 days ago. It didn't make sense that pnpm would also have the old create-vite-pages in its cache, unless it's somehow also using npm's cache behind the scenes. Oh and npm assured me that i shouldn't need to clean its cache when I tried to. So I quickly wrote that off.

Then I figured maybe it's the registry, and since yarn uses a different registry, that might work. And it did. Then I went back to npm to compare the outputs again and it also just worked. And so did pnpm. But I force-cleaned its cache anyway just for good measure.

from vite-plugin-react-pages.