[Bug?]: yarn does not respect publishConfig when using portal protocol

[fourdim]

Self-service

• I'd be willing to implement a fix

Describe the bug

I'm planning to use a local package for development.

It's package.json looks like this:

{
  "main": "src/index.ts",
  "type": "module",
  "scripts": {
    "build": "tsc",
  },
  "keywords": [],
  "exports": {
    "./src/*": "./src/*.ts",
    ".": "./src/index.ts",
  },
  "publishConfig": {
    "access": "public",
    "main": "dist/index.js",
    "types": "dist/index.d.ts",
    "exports": {
      "./src/*": "./dist/*.js",
      ".": {
        "types": "./dist/index.d.ts",
        "module": "./dist/index.js",
        "import": "./dist/index.js"
      }
    }
  }
}

(This package is inside a workspace, so we need it's non-publish exports default to ts file)

When linking this package to a project by:

yarn link -p ../workspace/project-name

All the imports are resolved to ts file but not js file after build.

To reproduce

yarn link -p ../workspace/project-name

Environment

System:
    OS: Linux 6.4 Arch Linux
    CPU: (12) x64 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
  Binaries:
    Node: 18.16.1 - /tmp/xfs-d4b44f58/node
    Yarn: 3.6.0 - /tmp/xfs-d4b44f58/yarn
    npm: 9.5.1 - ~/.config/nvm/versions/node/v18.16.1/bin/npm

Additional context

No response

[tomas-light]

Same to me. I use workspaces like:

project
│   package.json
│
└─── packages
│   └─── my-lib
│   │   └─── package.json
│   │   │   
│   │   └─── src
│   │   │   └─── index.ts
│   │   │
│   │   └─── dist
│   │       └─── index.js
│   │       └─── index.d.ts
│   │   
│   └─── my-tests-or-docs-or-something-else
│       │   └─── src
│       │   │   └─── index.ts

And it would be nice, If could use different export settings to use my-lib inside related workspaces and outisde, when it comes as a bundled package