v3.3.2

3.3.2 (2019-09-13)

Bug Fixes

• rename: don't accidentally file if new filename invalid (#26) (b6ac6b7)

v3.3.1

3.3.1 (2019-09-09)

Bug Fixes

• HttpBackend: fs.readFile should throw on 404s (#24) (34fac1b)

v3.3.0

3.3.0 (2019-06-24)

Features

• make threadsafe with mutex (#19) (3ec82a7)

v3.2.1

3.2.1 (2019-05-05)

Bug Fixes

• ignore trailing slash (#14) (eef9ad4)

v3.2.0

3.2.0 (2019-03-18)

Features

• add fs.promises (#12) (e47c9c1)

v3.1.0

3.1.0 (2019-03-18)

Features

• symlink support (#11) (3c6e803)

v3.0.3

3.0.3 (2019-01-17)

Bug Fixes

• fix awful inode autoincrement bug (587c741)

v3.0.2

3.0.2 (2019-01-17)

Bug Fixes

• 'rename' was forgetting to save the superblock (d7ab3c0)
• bind 'rename' to fs instance (24c4c05)

v3.0.1

3.0.1 (2019-01-17)

Bug Fixes

• remove console.log (4f604fa)

v3.0.0

3.0.0 (2019-01-17)

Features

• add 'rename' function (074547c)

BREAKING CHANGES

• The IndexedDB database format changed - the primary key is now an inode number rather than a filepath string. Adding this layer of indirection make renaming files and directories fast. (Before, renaming a directory would have required recursively copying all the files to a new location.) Rather than bloat the code with a migration script, I recommend simply creating a fresh filesystem or blowing the old filesystem away with the wipe argument. Maybe you can load v2 and v3 at the same time, and recursively read from the v2 instance and write to the v3 instance? Database migrations are hard, and I apologize. But this should be the first and last backwards incompatible change to the database format.
• the stat function now returns mtimeMs rather than mtimeSeconds and mtimeNanoseconds to match what Node's stat function returns instead of catering to an implementation detail of isomorphic-git.