fix a caching bug, which was a regression in 0.9.0 (issue #63)
update license attribute in package.json as required by npm
Thanks to Peter deHaan
construct GMT times used in tests in a more robust way
warn about possible misuse of %:: or %::: modifiers
This release marks the final run up to v1.0, which should be released by March 2016.
Along with this the API has been unified and cleaned up.
localizedStrftime have all been deprecated in favour of the following functions:
localize(locale). You use them like so:
var strftime = require('strftime'); // not required in web browsers var strftimeIT = strftime.localize(anItalianLocale); var strftimePST = strftime.timezone('-0800'); var strftimeUTC = strftime.utc(); // You can combine them var strftimeIT_PST = strftimeIT.timezone('-0800'); // And chain them all at once var strftimeIT_PST = strftime.localize(anItalianLocale).timezone('-0800');
The previous API is deprecated and will be removed for v1.0. The good news is that the previous API is supported by adapting the new API, so you get most of the performance benefits before you even update your code to use the new API.
The new API does not support passing in a custom timezone or locale on each call to
strftime. This is a regression so if you really need this use case let us know and we'll figure something out.
Thanks to all contributors that have helped to improve this library over the past 4 years.