bug: Path aliases are present in the generated type declarations

[sean-perkins]

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already report this problem, without success.

Stencil Version

v3.2.2

Current Behavior

When using path aliases, both the src/components.d.ts and dist/types/components.d.ts reference the alias path instead of the relative path.

// dist/types/components.d.ts
import { MaskVisibility } from "@utils/input-masking/types";
export { MaskVisibility } from "@utils/input-masking/types";

Expected Behavior

The generated type declaration file should be relatively pathed and all import aliases should be replaced.

import { MaskVisibility } from "./utils/input-masking/types";
export { MaskVisibility } from "./utils/input-masking/types";

System Info

System: node 16.15.1
    Platform: darwin (22.2.0)
   CPU Model: Apple M1 (8 cpus)
    Compiler: /Users/sean/Documents/ionic/issues/stencil-alias-imports/node_modules/@stencil/core/compiler/stencil.js
       Build: 1682947516
     Stencil: 3.2.2 🏒
  TypeScript: 4.9.5
      Rollup: 2.42.3
      Parse5: 7.1.2
      Sizzle: 2.42.3
      Terser: 5.17.1

Steps to Reproduce

1. Add a prop to a Stencil component, that has a type from an import alias.

import { MaskVisibility } from '@utils/input-masking/types';

...

@Prop() maskVisibility: MaskVisibility;

2. Run stencil build to generate the type declaration files.
3. Observe: The path aliases are still present in the compiled output.

Code Reproduction URL

https://github.com/sean-perkins/stencil-named-imports

Additional Information

No response

[rwaskiewicz]

The fix for this has gone out in today's Stencil v3.3.0 release. As a result, I'm going to close out this ticket. If the issue should reappear, please feel free to open a new issue. Thanks!