Skip to content

Releases: aem-vite/import-rewriter

v9.0.0

20 Nov 01:08
Compare
Choose a tag to compare

9.0.0 (2023-11-20)

Build System

  • drop native CJS support (5b7f4fc)
  • increase minimum node and vite versions (d3b0294)

BREAKING CHANGES

  • no longer support CJS

Vite 5 deprecates CJS support and as such support has been dropped here

  • bump min node and vite versions

Node v18/20 and Vite v5+ are required moving forward.

v8.0.0

14 Jul 15:27
Compare
Choose a tag to compare

8.0.0 (2023-07-14)

Build System

  • increase minimum node and vite versions (2d71162)

BREAKING CHANGES

  • bump min node and vite versions

Node v16 and Vite v3.0.0 are required moving forward.

v7.0.0

30 Nov 04:46
Compare
Choose a tag to compare

7.0.0 (2022-11-30)

Features

  • support multiple key formats for acs commons (4fe9015)

BREAKING CHANGES

  • Change default keyFormat handling

ACS Commons ships with two different ClientLib path formats. This change introduces support for both. Use acs-modern for instances where your ClientLibs contain ACSHASH and acs-classic when only the MD5 hash exists. For AEMaaCS please ensure you use cloud.

v6.0.1

29 Jul 15:50
Compare
Choose a tag to compare

6.0.1 (2022-07-29)

Bug Fixes

  • resolve incorect dynamic import paths (7fc8f92)

v6.0.0

02 Jul 02:22
Compare
Choose a tag to compare

6.0.0 (2022-07-02)

Build System

  • increase minimum node version (572b261)

BREAKING CHANGES

  • Increment minimum required node version to v14

As Node v12 is no longer supported we are bringing our minimum supported version of node to v14. Please ensure your project is up to date.

v5.0.1

26 May 08:22
Compare
Choose a tag to compare

5.0.1 (2022-05-26)

Bug Fixes

  • resolve incorrect plugin instance type (9ebc985)

v5.0.0

12 Feb 02:25
Compare
Choose a tag to compare

5.0.0 (2022-02-12)

Code Refactoring

Features

  • redesign imports handler (7b1ac3b)

BREAKING CHANGES

  • Complete redesign of the dynamic/native imports handler

The previous implementation was kind of clunky and didn't behave correct in most situations. A new resourcesPath configuration exists in the bundles rewriter which enforces a strict contract between the handler and your configuration, removing all assumptions.

Please refer to the below for how you should optimally setup your Vite configuration.

{
  base: command === 'build' ? '/etc.clientlibs/<project>/clientlibs/<clientlib>/' : '/',

  build: {
    rollupOptions: {
      output: {
        chunkFileNames: '<clientlib>/resources/js/chunks/[name].js',
        entryFileNames: '<clientlib>/resources/js/[name].js',
      },
    },
  },

  plugins: [
    bundlesImportRewriter({
      publicPath: '/etc.clientlibs/<project>/clientlibs/<clientlib>',
      resourcesPath: 'resources/js',
    }),
  ],
}
  • Vite 2.6.x and greater is now required

To keep up with internal fixes and feature additions Vite 2.6.x or greater is required to support server.origin which removes the need for the CSS Rewriter.

v4.1.3

20 Jan 01:01
Compare
Choose a tag to compare

4.1.3 (2022-01-20)

Bug Fixes

  • resolve AEM import path (bca085c)

v4.1.2

19 Jan 11:24
Compare
Choose a tag to compare

4.1.2 (2022-01-19)

Bug Fixes

  • resolve entry file import dependency paths (dda6521)

v4.1.1

19 Jan 05:58
Compare
Choose a tag to compare

4.1.1 (2022-01-19)

Bug Fixes

  • resolve import paths with caching enabled (f5c2a35)