diff options
| author |  Jarred Sumner <jarred@jarredsumner.com>
| 2021-10-06 19:26:28 -0700 |
|---|---|---|
| committer | Jarred Sumner <jarred@jarredsumner.com>
| 2021-10-06 19:26:28 -0700 |
| commit | 1e8babe1852361a2ace6c01dc699c08115462eba (patch) | |
| tree | 5cc8768401b38ead3b58a72b38e7dad20037f936 /integration/snapshots/spread_with_key.debug.tsx | |
| parent | 69d3b5ca605f3ce66b4e7441f0528618f81d7505 (diff) | |
| download | bun-1e8babe1852361a2ace6c01dc699c08115462eba.tar.gz bun-1e8babe1852361a2ace6c01dc699c08115462eba.tar.zst bun-1e8babe1852361a2ace6c01dc699c08115462eba.zip | |
HTTP paths must resolve from ./$PROJECT_ROOT unless explicitly marked absolute.
This fixes the issue with deeply nested PNPM workspace packages. Happened when using @emotion/react inside a PNPM workspace when @emotion/react was hoisted to the workspace root but react was in a child node_modules folder. It would fail to resolve `"react/jsx-dev-runtime"` because it didn't exist in any node_modules folder relative to `@emotion/react`'s real path.
Diffstat (limited to 'integration/snapshots/spread_with_key.debug.tsx')
0 files changed, 0 insertions, 0 deletions