fix(core): fix a bug where a package's code could not load its own package

[nabetti1720]

Description of changes

For example, when react-dom/server.edge was called, this issue occurred because react-dom was required again inside the package.

// reproduction.js
import * as dom from "react-dom/server.edge";
console.log(dom);

% llrt reproduction.js 
Error: IO Error: No such file or directory (os error 2)
  at <anonymous> (__cjs:/Users/shinya/Workspaces/llrt-test/node_modules/react-dom/cjs/react-dom-server.edge.development.js:7330:18)
      at <anonymous> (__cjs:/Users/shinya/Workspaces/llrt-test/node_modules/react-dom/cjs/react-dom-server.edge.development.js:8975:3)
      at <anonymous> (__cjs:/Users/shinya/Workspaces/llrt-test/node_modules/react-dom/server.edge.js:9:7)

% bun reproduction.js
Module {
  default: {
    version: "19.0.0",
    renderToReadableStream: [Function],
    renderToString: [Function],
    renderToStaticMarkup: [Function],
  },
  renderToReadableStream: [Function],
  renderToStaticMarkup: [Function],
  renderToString: [Function],
  version: "19.0.0",
}

This PR fixes this by storing the correct path when referencing self, to avoid IO errors.

Checklist

• Created unit tests in tests/unit and/or in Rust for my feature if needed
• Ran make fix to format JS and apply Clippy auto fixes
• Made sure my code didn't add any additional warnings: make check
• Added relevant type info in types/ directory
• Updated documentation if needed (API.md/README.md/Other)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[richarddavison]

Thanks! Looks like there is some Windows issue with path / replacement?

[nabetti1720]

Thanks! Looks like there is some Windows issue with path / replacement?

It seems that's the case, but I haven't yet found the cause, so I'll need to investigate further...