4 people reported
All time, since Aug 22.
Import misses newly created files
“1.4.0 (also reproduced on 1.3.14 — not a regression, see below)”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/bun/issues/4749/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Dynamic import misses files added to an already-resolved directory. Fails with "Cannot find module" though existsSync confirms the file; parent directory's module listing appears cached.
Is this your bug?
File my report- Where
- module resolution
- Error text
error: Cannot find module '/private/var/folders/…/T/bun-dircache-XXXX/b.mjs' from ''- Versions
- 1.4.0 to 1.4.2
- Platforms
- macOS
- How bad
- Breaks a normal workflow. Some reports say it used to work.
Not quite your bug?
Original reports4, newest first
- Dynamic import of an absolute path fails with "Cannot find module" when the file was written after an earlier import from the same directory#44225
import()of a newly created sibling module fails: parent directory's module listing appears cached#40790- require()/import() fails on the first resolution of a second fresh sibling .ts file per process, from '' error#40585
- import() cannot see a file created in a directory that was already resolved once (not a 1.4 regression)#40105