- Fixed: ensure node 0.12 compatibility, round 2 (#93)
- Fixed: performance issue because of cloned options (#90)
- Added: ensure node 0.12 compatibility
- Removed: compatibility with postcss v4.x (#75)
- Added: compatibility with postcss v5.x (#76)
- Added: lighter package by upgrading some dependencies (#73)
- Added:
skipDuplicates
option now allows you to not skip duplicated files (#67)
- Fixed: Prevent mutability issue, round 2 (#44)
- Added:
plugins
option, to run some postcss plugin on imported files (#55) - Added:
bower_components
is now part of the default paths (#66) - Added:
async
option allow to use enable PostCSS async API usage. Note that it's not enabling async fs read yet. It has been added to fix breaking change introduced by 6.1.0.
This release was not respecting semver and introduced a major breaking change. It has been unpublished for now.
- Changed: warnings messages are now using postcss message api (4.1.x)
- Added: warning when a import statement has not been closed correctly (#42)
- Fixed: globbed imports work for module directories (#37)
- Fixed: glob import now works with single quote
@import
(#36)
- Added: glob pattern are now supported if
glob
option is set to true (#34) - Added: plugin can now be added to PostCSS without calling it as a function (#27)
- Fixed: regression of 5.1.0: files which only contain same @import rules were skip (#31)
- Added: files with the same content will only be imported once. Previously, only the full path was used to determine if a file has already been imported in a given scope.
Now, we also test create a hash with the content of the file to check if a file with the same content has not already been imported.
This might be usefull if some modules you import are importing the same library from different places (eg: normalize might be as dep for several modules located in different places in
node_modules
) (#29)
- Fixed: regression of 5.0.2: AST parent references were not updated (#25)
- Fixed: indentation and code style are now preserved (#20)
- Added: compatibility with postcss v4.x
- Removed: compatibility with postcss v3.x
- Fixed: relative imports (./ and ../) should work using
path
option only (no need forfrom
) (#14)
- Fixed: irregular whitespace that throw syntax error in some environnements
- Added:
web_modules
is now in module directories that are used to resolve@import
(#13).
- Added: windows compatibility (by building on AppVeyor)
- Added:
root
option
- Added:
onImport
callback offers a way to get list of imported files (ref)
- Added: ability to consume local modules (fix #12)
- Added: ability to consume node modules (ref).
This means you don't have to add
node_modules
in the path anymore (or using@import "../node_modules/..."
). Also,index.css
can be ommited.
This means something like this
@import "../node_modules/my-css-on-npm/index.css";
can be written like this
@import "my-css-on-npm";
Dependencies of dependencies should be resolved as well.
Note that npm resolution is done after the default local behavior.
- Changed: When importing a file multiple times in the same scope (same level of media queries), file will only be imported the first time. This is done to avoid having multiples outputs of a npm dep used multiples times in different modules.
- Added: compatibility with postcss v3.x
- Removed: compatibility with postcss v2.x
- Fixed: relative import path stack
- Added: Move ignored import at top & adjust related media queries, to make them work (fix #2)
- Added: Ignore scheme-relative absolute URLs
- Removed:
parse-import
module dependency
- Fixed: GNU message format
- Added: Support empty files (cssnext/#24)
✨ First release based on rework-import v1.2.0 (mainly for fixtures)