fix(package.json): edit main, exports and publishConfig to improve DX

[manudeli]

Edit main, exports and publishConfig to improve DX

Cannot find module directly, if contributors didn't build packages.

Though there is built packages, Contributor want to access source itself, not built package.

Solution I thought

How about making vscode access to workspaces source code directly, not built package. if package.json using publishConfig, making built package and developing package in workspaces for DX separately is available.

{
  "main": "src/index.ts",
  "exports": {
    ".": {
      "require": "./src/index.ts",
      "import": "./src/index.ts"
    },
    "./package.json": "./package.json"
  },
  "publishConfig": {
    "access": "public",
    "exports": {
      ".": {
        "require": "./dist/index.js",
        "import": "./esm/index.mjs",
        "types": "./dist/index.d.ts"
      },
      "./package.json": "./package.json"
    },
    "import": "./esm/index.mjs",
    "main": "./dist/index.js",
    "types": "dist/index.d.ts",
    "module": "esm/index.mjs"
  },
}

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[netlify]

✅ Deploy Preview for storybook-h6s ready!

Name	Link
🔨 Latest commit	5d99463
🔍 Latest deploy log	https://app.netlify.com/sites/storybook-h6s/deploys/63a288cab9ae0200092bae2f
😎 Deploy Preview	https://deploy-preview-228--storybook-h6s.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

✅ Deploy Preview for h6s-react-examples canceled.

Name	Link
🔨 Latest commit	5d99463
🔍 Latest deploy log	https://app.netlify.com/sites/h6s-react-examples/deploys/63a288caab5e16000897191b

[netlify]

✅ Deploy Preview for h6s-dev canceled.

Name	Link
🔨 Latest commit	5d99463
🔍 Latest deploy log	https://app.netlify.com/sites/h6s-dev/deploys/63a288ca7d15890008bc5587

[SoYoung210]

Thanks for Contribute.

I would appreciate it if you could change the order of the exports fields(types first) by referring to below information. 👇
microsoft/TypeScript#46334

cc @JaeYeopHan

[manudeli]

Thanks for Contribute.

I would appreciate it if you could change the order of the exports fields(types first) by referring to below information. 👇 microsoft/TypeScript#46334

cc @JaeYeopHan

@SoYoung210

I changed order of exports as your link reference's advice.

I tried to reproduce problem situation. but actually, I couldn't reproduce it what you worried. so I couldn't get confidence at this implementation. If my change is wrong, could you make some suggestion code for me? I just want to know what you want exactly.

[SoYoung210]

I don't know how you tried it, but as written in the issue above, in an environment using (ts)module: next and wrong order of the exports map - types are not described first, the type evaluation can match the wrong file.

btw, i'll investigate broken netlify issues... I don't think it's because of this change 🤔, but can you wait a moment? 🙏 🙏

[SoYoung210]

@manudeli netlify issue is solved in #231. I'll rebase this PR and publish beta release for testing.

[JaeYeopHan]

rebase please

[SoYoung210]

@manudeli sorry i cant rebase this pr (this pr is created through a forked repo 😅)
can u do it?

[manudeli]

@JaeYeopHan @SoYoung210 Rebasing done

[github-actions]

🎉 This PR is included in version @h6s/calendar-v1.0.8-alpha.1 🎉

[github-actions]

🎉 This PR is included in version @h6s/table-v1.0.5-alpha.1 🎉