Skip to content

chore: add top-level types field to package.json - #951

Closed
psfazila02-hub wants to merge 0 commit into
nuxt-hub:mainfrom
psfazila02-hub:add-types-field
Closed

psfazila02-hub wants to merge 0 commit into
nuxt-hub:mainfrom
psfazila02-hub:add-types-field

Conversation

@psfazila02-hub

Copy link
Copy Markdown
Contributor

Declares "types": "./dist/types.d.mts" at package.json root to ensure TypeScript resolves module types correctly under legacy and Node10 moduleResolution modes.

@vercel

vercel Bot commented Nov 2, 2026

Copy link
Copy Markdown

@psfazila02-hub is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.

atinux commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Thanks! I moved types next to main.

Note that the impact is small: this only changes TypeScript's legacy node10 resolution, where @nuxthub/core previously resolved to dist/module.d.mts (via main) instead of dist/types.d.mts. With bundler or node16 (what Nuxt projects use), exports already points to types.d.mts. And since types.d.mts re-exports everything from module.mjs, node10 users only missed the #app / @nuxt/schema hooks and runtime config augmentations, not any exports.

Written by an AI agent (Amp) on behalf of @atinux.

@atinux atinux changed the title Add top-level types field to package.json chore: add top-level types field to package.json Nov 2, 2026
@pkg-pr-new

pkg-pr-new Bot commented Nov 2, 2026

Copy link
Copy Markdown
npm i https://pkg.pr.new/@nuxthub/core@951

commit: 2220a74

atinux commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Sorry @psfazila02-hub, this PR got closed by mistake: a force-push meant to squash the commits overwrote your branch with main, and GitHub closed the PR because it had no changes left. It couldn't be reopened or pushed to after that.

The change continues in #952 as a single commit that credits you as co-author.

Written by an AI agent (Amp) on behalf of @atinux.

This branch was successfully deployed

2 active deployments
Production — bf1852db Deployed Oct 27, 2026 by vercel[bot]
npm — bf1852db Deployed Oct 27, 2026 by github-actions[bot] via publish #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants