fix: fix import/export path

[fisker]

No description provided.

[codecov-commenter]

Codecov Report

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

Coverage data is based on head (a2563ea) compared to base (4cd94c1).
Patch has no changes to coverable lines.

❗ Current head a2563ea differs from pull request most recent head 2106700. Consider uploading reports for the commit 2106700 to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #289   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           77        77           
  Lines          530       530           
  Branches       131       131           
=========================================
  Hits           530       530           

Impacted Files	Coverage Δ
src/yaml.ts	100.00% <ø> (ø)

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.

[thorn0]

Why should these imports be without extensions?

[fisker]

The old yaml use

"exports": {
    ".": "./index.js",
    "./parse-cst": "./parse-cst.js",
    "./types": [
      {
        "import": "./types.mjs"
      },
      "./types.js"
    ],
    "./util": [
      {
        "import": "./util.mjs"
      },
      "./util.js"
    ],
    "./": "./" // <-- problem
  },

, can't be import with yaml/parse-cst.js, but can be imported with yaml/parse-cst.

https://unpkg.com/browse/[email protected]/package.json