Skip to content

Releases: Galooshi/import-js

v1.1.2

14 Dec 12:40
Compare
Choose a tag to compare

This version fixes an issue with goto not resolving to the right file path.

v1.1.1

01 Sep 21:23
Compare
Choose a tag to compare

v1.1.0

20 Aug 15:37
Compare
Choose a tag to compare

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

05 Jul 18:37
Compare
Choose a tag to compare

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

01 Jul 19:09
Compare
Choose a tag to compare

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

0.8.0

29 May 17:20
Compare
Choose a tag to compare

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

0.7.4

24 May 08:12
Compare
Choose a tag to compare

Changes:

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

0.7.3

20 May 14:57
Compare
Choose a tag to compare
  • 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

11 May 13:17
Compare
Choose a tag to compare

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

0.7.1

11 May 09:33
Compare
Choose a tag to compare

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.