NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #1729 most downloaded on npm
Date formatting and parsing
Last release 4 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 13 months
Most releases are documented
notes for 14 of 22 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
25 releases · first in 2015
Fixed bug with UTC date on daylights savings time #94
Nothing published for this version
- Fixed missing source map - Fixed security y18n
One column per quarter.
Added isoDate and isoDateTime masks
Added isoDate and isoDateTime masks
Added Z format token. See readme for more info. Big thanks to @fer22f for writing the code.
Z format token. See readme for more info. Big thanks to @fer22f for writing the code.Added Z format/parse and fixed Peru timezone issue
Z format token. See readme for more info. Big thanks to @fer22f for writing the code.Major Features and Breaking changes in this version
2019-55-01 or 2019-01-42 would parse correctly, since Javascript can handle it. Now invalid dates will return null insteadparse or format independentlyimport {format, parse} from 'fecha';
format(...);
parse(...)
parseDate may return null when previously returned a Date. See improvements above, but invalid dates will return null nowimport fecha from 'fecha';
fecha.i18n = { ... }
fecha.masks.myMask = 'DD , MM, YYYY'
New
import {parse, format, setGlobalDateI18n, setGlobalDateMasks} from 'fecha';
setGlobalDateI18n({
// ...
})
setGlobalDateMasks({
myMask: 'DD , MM, YYYY'
});
Breaking Changes in this release No changes from alpha and beta. See 4.0.0-alpha for full change log.
Breaking Changes in this release No changes from alpha and beta. See 4.0.0-alpha for full change log.
Nothing published for this version
*Valid date parsing* - By default fecha will check validity of dates. Previously 2019-55-01 or 2019-01-42 would parse correctly, since Javascript can
2019-55-01 or 2019-01-42 would parse correctly, since Javascript can handle it. Now invalid dates will return null insteadparse or format independentlyimport {format, parse} from 'fecha';
format(...);
parse(...)
parseDate may return null when previously returned a Date. See improvements above, but invalid dates will return null nowimport fecha from 'fecha';
fecha.i18n = { ... }
fecha.masks.myMask = 'DD , MM, YYYY'
New
import {parse, format, setGlobalDateI18n, setGlobalDateMasks} from 'fecha';
setGlobalDateI18n({
// ...
})
setGlobalDateMasks({
myMask: 'DD , MM, YYYY'
});Nothing published for this version
Fixed bug when using brackets when parsing dates
Fixed issue where src files are not included correctly in npm
Changed invalid date from false to null
false to nullFixed bug with year 999 not having leading zero
Fixed bug with year 999 not having leading zero
Added typescript definitions to NPM
Added typescript definitions to NPM
Nothing published for this version
Added literal support to fecha. https://github.com/taylorhakes/fecha/issues/18
Added literal support to fecha. https://github.com/taylorhakes/fecha/issues/18
Thanks @antivanov
Added strict version of date parser that returns null on invalid dates (may use strict version in v3)
Fixed a bug when parsing dates with 10th, 12th, 1st, etc.
Fixed a bug when parsing dates with 10th, 12th, 1st, etc.
Fixed a bug when parsing Do format dates
Fecha now throws errors on invalid dates in fecha.format and is stricter about what dates it accepts. Dates must pass Object.prototype.toString.call(dateObj) !== '[object Date]'.
Nothing published for this version
Fecha will now throw errors if you try to format a Date object that is not valid. This helps in debugging and not allowing invalid dates being shown t
Nothing published for this version
Nothing published for this version
Nothing published for this version
Removed ability to use Fecha.parse without format parameter
Breaking Changes:
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →