Releases: lukeed/sirv
v3.0.0
Breaking
Features
- Added
node:
prefix for explicit native imports, which unlocks Deno support (#163): 912af6f
Thank you @karimfromjordan
Patches
- Add separate CJS and ESM definitions: 982fcc8
Previously CJS types were wrong/incompatible.
Chores
- (sirv-cli) Upgrade
get-port
to 5.1.1 for TS definitions: e5e0826 - Write tests in native ESM: 2f36733
- (CI): Add Node 20 to matrix: 9ca1cbc
Full Changelog: v2.0.4...v3.0.0
v2.0.4
Patches
- (
sirv
) bumpmrmime
version (#156): ed8fd84
Seemrmime@2.0.0
release notes for info.
Thank you @benmccann
Full Changelog: v2.0.3...v2.0.4
v2.0.3
Patches
- fix(sirv): avoid false-positive on too big range end by @dmkret in #147
- fix(sirv): correctly decode path by @benmccann in #149
Full Changelog: v2.0.2...v2.0.3
v2.0.2
v2.0.0
Breaking
- (sirv-cli) Change default port from
5000
to8080
(#124): 93a920b
With macOS Monterey, Apple now reserves port 5000 for AirPlay. This would causesirv-cli
to start seemingly successfully, but macOS would intercept all traffic tolocalhost:5000
, causing unexpected behavior for users/clients.
Features
-
(sirv): Supports native ESM usage within Node~!
Nowsirv
and all its dependencies support ESM natively. -
(sirv-cli): Support the
NO_COLOR
standard (#108): 4b8703b
Thank you @SpyTec~!
Chores
-
(sirv): Bump
totalist
version (#86): 0cf66d8
Thank you @aleclarson~! -
Add
http-server
benchmark comparison (#4): 17ea37fhttp-server (cache=1) 5,247 req/sec http-server (cache=0) 5,091 req/sec sirv-cli (cache=1) 12,612 req/sec sirv-cli (cache=0) 8,490 req/sec sirv-cli (cache=1, logs=0) 13,609 req/sec sirv-cli (cache=0, logs=0) 10,157 req/sec
Full Changelog: v1.0.19...v2.0.0
v1.0.19
v1.0.18
Patches
- (sirv): Append
charset=utf-8
to HTML content-type (#106, #122): d1b8ba6
Thank you @aleclarson~!
Full Changelog: v1.0.17...v1.0.18
v1.0.14
v1.0.13
Patches
-
(
sirv
) Only usereq.path
if hasreq._decoded
flag exists (#82):The
req._decoded
check was added & should have always been in there, since this wassirv
's way of preventing duplicatedecodeURIComponent
calls. However, this was only true when it received a request from apolka@next
app, since Polka was previously writing the decoded value toreq.path
– this changed withpolka@v1.0.0-next.16
Now that the latest
polka@next
(and Express) doesn't decode automatically anymore,req.path
isn't trustworthy on its own. It needsreq._decoded
to be there too in order to trust it.This combo-check is backwards compatible for
polka@next
users who don't upgrade and will unblock Express users for the first time, who have always had a "raw"req.path
value set.