failing setup

[rchl]

Following setup steps fails when running pnpm i:

. pnpm:devPreinstall$ npm run prepare:framework && npm run clean
│ > prepare:framework
│ > cd framework && pnpm i && npm run build
│ Scope: all 13 workspace projects
│ Lockfile is up to date, resolution step is skipped
│ Already up to date
│ Done in 843ms
│ > build
│ > tsc -b
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
│ tsconfig.json(3,2): error TS5102: Option 'importsNotUsedAsValues' has been removed. Please remove it from your configuration.
│   Use 'verbatimModuleSyntax' instead.
└─ Failed in 2.5s at /usr/local/workspace/github/volarjs
 ELIFECYCLE  Command failed with exit code 1.

[rchl]

After removing that setting there is a type issue on building like:

│ packages/language-service/lib/utils/uriMap.ts(28,4): error TS2322: Type '() => Generator<URI, void, unknown>' is not assignable to ty…
│   Call signature return types 'Generator<URI, void, unknown>' and 'MapIterator<URI>' are incompatible.
│     The types returned by 'next(...)' are incompatible between these types.
│       Type 'IteratorResult<URI, void>' is not assignable to type 'IteratorResult<URI, undefined>'.
│         Type 'IteratorReturnResult<void>' is not assignable to type 'IteratorResult<URI, undefined>'.
│           Type 'IteratorReturnResult<void>' is not assignable to type 'IteratorReturnResult<undefined>'.
│             Type 'void' is not assignable to type 'undefined'.

I will never understand how this setup works ;)

[rchl]

I've figured out that this issue is due to bumping dependency versions (including typescript) in the lock file.

So then my questions are:

• why do the framwork, services, vue, etc. repos don't pin the dependencies so that the things don't break when package lock is refreshed? For example typescript range is specified as latest.
• why not use dependabot or renovate for bumping dependencies and making sure that any dependency updates go through CI (to avoid broken commits like volarjs/volar.js@eb9864d)?

The dependencies being locked would also help in pnpm linking dependencies to local repos since it can't link if there is existing pnpm-lock file pointing at upstream packages. The lock file needs to be deleted for pnpm to link local ones.