Closed karlhorky closed 1 week ago
hi @karlhorky, thanks for the kind words!
I'm not very familiar with pnpm, but the @extension-create/develop
is a top-level dependency of extension
and is basically the whole package dev experience, so having it as a project top-level dependency would be redundant at the moment.
From what you said it seems that moving the types to the core package "extension" would fix the issue? Like <refrence types="extension/dist/types/index.d.ts" />
. This would be more doable as a fix.
From what you said it seems that moving the types to the core package "extension" would fix the issue? Like
<refrence types="extension/dist/types/index.d.ts" />
. This would be more doable as a fix.
That would be one alternative, yep!
A bit more background: Referencing anything that is not a direct dependency of the user's project will error out as unresolvable with pnpm (and other package managers, if I remember correctly).
So referencing extension
(which is a top-level dependency in the user's package.json
) should be no problem.
Thanks so much for Extension! Great developer experience π
A TypeScript error
TS2307: Cannot find module
is thrown on a fresh app after using pnpm (pnpx
alias forpnpm dlx
) along withextension@latest create <name> --template=react-typescript
to scaffold:This appears to be caused by
@extension-create/develop
not being a top-level dependency inpackage.json
(so this is not hoisted tonode_modules
by pnpm):extension-env.d.ts
pnpm directory structure:
Would you consider adding
@extension-create/develop
(and any other dependencies that should be innode_modules
at the top level) as a direct dependency in the generatedpackage.json
?