TypeScript Declarations not found when using export maps

Describe the bug Suppose I have a npm package named package. The package.json of package looks like:

{
  "name": "package",
  "version": "1.0.0",
  "main": "index.js",
  "types": "./types/index.d.ts",
  "exports": {
    ".": {
      "default": "./index.js"
    },
    "./Component": {
      "default": "./Component.svelte"
    }
  }
}

The types directory in package looks like:

- index.d.ts
- Component.d.ts

The content of Component.d.ts is:

/// <reference types="svelte" />
import { SvelteComponentTyped } from 'svelte';

export interface Props {
  /**
   * @default "svelte"
   */
  prop?: string;
}

export default class Component extends SvelteComponentTyped<Props, {}, {}> {}

Now in my app where I have svelte with typescript with the content of the tsconfig.json as

{
  "extends": "@tsconfig/svelte/tsconfig.json",
  "compilerOptions": {
    "moduleResolution": "node",
    "module": "es2020",
    "lib": ["es2020"],
    "target": "es2019",
    "importsNotUsedAsValues": "error",
    "isolatedModules": true,
    "resolveJsonModule": true,
    "sourceMap": true,
    "esModuleInterop": true,
    "skipLibCheck": true,
    "forceConsistentCasingInFileNames": true,
    "baseUrl": ".",
    "allowJs": true,
    "checkJs": true
  },
  "include": ["src/**/*"]
}

and my svelte.config.js is:

const sveltePreprocess = require('svelte-preprocess');

module.exports = {
  preprocess: sveltePreprocess(),
};

And in my Svelte file I import package/Component:

To Reproduce

• Clone https://github.com/TheComputerM/langserver-ts-bug
• Using PNPM run pnpm i
• RUN cd app
• Open in VSCode
• Open src/Page.svelte
• See Error

Expected behavior No ts error

Information about your project:

• Windows 10
• svelte-preprocess version 4.7.3

[dummdidumm]

Fixed on master already, release soon

[dummdidumm]

Fixed with the latest release. Note that you need to set "moduleResolution": "node16" (or “nodenext”) in your tsconfig in order for the export map to get noticed - this has some other implications on relative import paths though, more about that in #1522