Skip to content

Releases: shellscape/webpack-nano

v1.0.0

23 Mar 01:15
Compare
Choose a tag to compare

Maintenance Release

This release contains dependency updates.

Breaking Changes

Because we've updated to a new major version of yargs-parser and we export the parsed result from that package in the webpack-nano/argv export, users may experience slightly different results. As such, we felt a major version release was best in light of that.

v0.8.0

18 Sep 13:43
Compare
Choose a tag to compare

Features

  • add argv typings for TypeScript (#15)

v0.7.1

21 Jul 16:34
Compare
Choose a tag to compare

Bugfixes

  • fix: import-local regression in v3.0.0 (1faa7d5)

v0.7.0

21 Jul 01:04
Compare
Choose a tag to compare

Breaking Changes

  • This release drops support for Node v8 (now in LTS maintenance)

v0.6.3

21 Jul 00:54
Compare
Choose a tag to compare

Updates

  • Maintenance. Dependency update.

v0.6.2

04 May 19:23
Compare
Choose a tag to compare

Updates

  • Dependency updates and npm audit fixes.

v0.6.1

03 Jan 16:52
Compare
Choose a tag to compare

Bugfixes

  • fix: handle default export. (#8)

v0.6.0

13 Dec 18:38
Compare
Choose a tag to compare

Features

  • feat: allow config transpiling (babel, typescript, etc) (#6) …

v0.5.1

13 Dec 18:39
Compare
Choose a tag to compare

Bugfixes

  • fix: detect duplicate builds and prevent duplicate output (a06b3cc)

v0.5.0

06 Dec 13:26
Compare
Choose a tag to compare

Breaking Change

#2 Proposed that stats output colors in the console should be on by default, as this was expected behavior for the webpack ecosystem, despite webpack's own default setting having colors turned off. Commit bfa757a introduced an algorithm whereby colors are enabled if:

  • colors is not defined in any stats configuration, or
  • stats is not an object

The same commit also introduced excluding node_modules in stats output in the same manner under the same conditions.