fix: make typescript a peer dependency #563
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes snowballed a bit but to summarize:
typescript
is now a peer dependency for bothtypescript-build
andtypescript-runtime
.Using latest
typescript
triggered a warning for the@typescript-eslint/eslint-plugin
as it was too old so updated@nuxtjs/eslint-config-typescript
andeslint
to latest veersions. This triggered some new eslint warnings so ignored those.There were also issues related to using
latest
versions inpackage.json
's as those were picking too new versions that were not compatible. For examplevue-property-decorator
was on some not-publicly-released version 10 that was triggering errors in test fixtures.Updated
nuxt
dependencies to use Nuxt v2 as it would pick Nuxt 3 otherwise. Also had to switch fromnuxt-edge
tonuxt
for now because nuxt/nuxt#19526 is not yet fixed. I can revert that later once things are in order again.Resolves #512
Resolves #557
Resolves #560