search

oven-sh / bun

Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
https://bun.sh
Other
73.15k stars 2.68k forks source link

Bunx force update cache #12245

Open CodeFromAnywhere opened 2 months ago

CodeFromAnywhere commented 2 months ago

What is the problem this feature would solve?

Screenshot 2024-06-29 at 10 35 41

The screenshot says enough. It cached 0.0.3 or so, and because I called 0.0.7 when it didn't exist yet, it remembers that even if it later DOES exist

What is the feature you are proposing to solve the problem?

When I publish a new version of my package, I want it to not cache things.

I am proposing a --no-cache feature that would force re-fetching the package.

Furthermore, I think it wouldn't hurt to do this once in a while anyway. If I specify the version with @x.x.x and later I run it without @x.x.x, it will not take the latest version but the first one it installed.

What alternatives have you considered?

I couldn't find a way to fix this yet. Maybe I can clean the global cache of bun entirely?

For now, I've changed my version to 0.0.10, published, and used bunx with @0.0.10. Now it works.

paperdave commented 2 months ago

Maybe I can clean the global cache of bun entirely?

not cleanly documented however bun pm cache rm clears bunx caches in addition to bun install caches. we should make it possible to clean just the bunx cache, as well as a temporary no-cache flag.