v1.1.1

• Fix importing inside anonymous files
  Galooshi/sublime-import-js#14

v1.1.0

Features:

• Add support for imports with side-effects. This adds a new
  configuration option moduleSideEffectImports that can be used to
  auto-inject these imports when running fix-imports.
• Add moduleNameFormatter configuration option.
• Add meteor environment.
• Add support for JavaScript configuration files and allow configuration
  options to be functions.
• Add importjsd logpath.

Deprecations:

• Deprecate .importjs.json in favor of .importjs.js.

Fixes:

• Prevent normalizePath from skipping dot-files.

v1.0.1

Changes:

• Support for a dynamic working directory (needed by the Atom plugin)
• New meteor environment (work still under progress to fully support Meteor)

Dev changes:

• Update to Jest 13

v1.0.0

This version is focused on speeding up ImportJS. Key changes:

• The process of finding modules in the file system is now parallellized. This means faster uses of fix-imports.
• ImportJS can be used as a background daemon process. The new importjsd command is meant to be used by editor plugins. Look for updates to https://github.com/Galooshi/vim-import-js, https://github.com/Galooshi/sublime-import-js, and https://github.com/Galooshi/emacs-import-js utilizing the new daemon (coming shortly).
• New integration with Watchman. If you have it installed, we'll make use of it to speed up importing (by a great deal!)

0.8.0

This version adds support for running import-js on Windows machines.

0.7.4

Changes:

• Fix goto not working correctly in Sublime
• Fix relative imports for named exports and aliases

0.7.3

• Fix bug that prevented paths to files within packages from being resolved correctly for goto.
• Add flow annotations
• Remove underscore from dependencies
• Update dependencies
• Improve mocking strategy in tests

0.7.2

Fixes an issue with how we read file content from stdin.

0.7.1

Breaking change: all configuration keys are now camelCased instead of snake_cased.

Hotfix for relative paths. They weren't working as they should when the path to the current file was passed in with an absolute path (e.g. /home/apps/todo-list/foo.js). This should fix issues with relative paths in the Sublime plugin.

0.6.0

Two new configuration options added in this release:

• group_imports - set to false to disable the default behavior of grouping imports
• environments - set to ["node"] to get access to core modules for Node.js

Apart from that, the Sublime plugin should now be easier to get up and running thanks to work by @lencioni.