search

browserify / wzrd.in

browserify as a service.
http://wzrd.in
MIT License
639 stars 96 forks source link

force cache bust #23

Closed max-mapper closed 11 years ago

max-mapper commented 11 years ago

for example, I installed the hypernal module, but it was buggy, so I sent the maintainer a pull req, they published a new version, but now I can't get hypernal@latest to install the newest version

jfhbrook commented 11 years ago

hmm. How should I do this? Is this an http header kind of thing?

jfhbrook commented 11 years ago

Notes to self:

I see a few solutions. 1) Make "latest" not cache, look up semver on npm with each request (should be correct each time); 2) Implement support for http cache headers (probably the most correct way, but a little involved); 3) "tough."

jfhbrook commented 11 years ago

4) Use npm-publish-stream to proactively clear the cache on changes

max-mapper commented 11 years ago

i like 4

On Thu, Jul 11, 2013 at 8:02 PM, Joshua Holbrook notifications@github.comwrote:

4) Use npm-publish-stream to proactively clear the cache on changes

— Reply to this email directly or view it on GitHubhttps://github.com/jesusabdullah/browserify-cdn/issues/23#issuecomment-20854477 .

jfhbrook commented 11 years ago

I implemented this on master, afaik it works.