fix(types): import Location from vue-router

[h-kishi]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Fixed vue-router's Location type was not imported and global Location type was used for redirect argument type.

https://github.com/nuxt/nuxt/blob/2.x/packages/types/app/index.d.ts#L60-L61

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[danielroe]

Thanks!

[codecov-commenter]

Codecov Report

Base: 66.42% // Head: 66.42% // No change to project coverage 👍

Coverage data is based on head (c26be57) compared to base (daed62a).
Patch has no changes to coverable lines.

Additional details and impacted files

@@           Coverage Diff           @@
##              2.x   #18908   +/-   ##
=======================================
  Coverage   66.42%   66.42%           
=======================================
  Files          93       93           
  Lines        4080     4080           
  Branches     1154     1154           
=======================================
  Hits         2710     2710           
  Misses       1107     1107           
  Partials      263      263           

Flag	Coverage Δ
unittests	66.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[tjhiggins]

Could you publish the nuxt type pkg? Hitting this issue now

[danielroe]

It should already be published.

[tjhiggins]

It should already be published.

My bad. For whatever reason it didn't show up when I ran npm outdated, but I see on npm page. Thanks.

[blimmer]

I was also confused about the type packages not being published - it looks like they're not being marked as latest anymore, so tools like npm outdated, npm-check-updates, yarn upgrade-interactive, etc. don't show an upgrade past 2.16.0 as available.

Since v3 doesn't require the types package, could we keep publishing types for 2.x as latest?

[danielroe]

Indeed. That's already been fixed in the release script and the next version will be tagged as latest.