content-disposition
3.0.0 · 13 Aug 2026MIT211.4M / weekRepositoryHomepagenpmAtom feed
Upgrading content-disposition From 0.0.0 to 3.0.0
17 releases in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 10
- new
- 5
- fixes
Before you upgrade
Tick each one off as you go- breaking2.0.0
- breaking1.0.1
- breaking1.0.0
Release by release
3.0.0nothing new or fixed in the note
- new
Allow empty param values in quoted text (#133) 5d5d71c
- new
- breaking
Invalid UTF-8 is no longer supported
- new
Expose
formatmethod (#129) 2bb7da3 - new
Allow extended parsing to be disabled (#130) c6b15c8
- new
Add HTML multipart behavior compatibility (#131) 3d217fb
- breaking
1.1.0nothing new or fixed in the note
- breaking
Update package.json engines field to reflect minimum supported node version
- fixed
Fix badges
- breaking
0.5.3 – 0.5.42 releases, nothing new or fixed in the notes
- fixed
Fix
parseto accept any linear whitespace character
- fixed
22 other lines we could not sort, mostly version bumps
- 3.0.0
Export package as ESM (#141)
- 3.0.0
Reject invalid percent-encoding in ISO-8859-1 ext-value (#138)
- 3.0.0
Skip duplicate parameter in extended format (#144)
- 2.0.1
Use first extended param (#136) fad11ba
- 2.0.1
Update RFC references (#134) a43fd35
- 2.0.0
Rename exports (#123) ec3a844
- 2.0.0
Removed
basenamefromcreate, pass a filename instead of a full path - 2.0.0
Refactor parser to be faster and lenient (e.g. now parses unicode)
- 2.0.0
Change filename in
createto ASCII only (#132) 3190b76 - 2.0.0
Null object performance bump (#124) 7c7c9c0
15 internal lines (docs, tests, tooling) left out.