chore(deps): update dependency @cultureamp/package-bundler to v4

[cultureamp-renovate]

Working with Renovate for Culture Amp

• Renovate Guide
• Renovate Troubleshooting
• Renovate How-tos

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@cultureamp/package-bundler (source)	^2.4.4 -> ^4.0.1

---

Release Notes

cultureamp/frontend-foundations (@​cultureamp/package-bundler)

v4.0.1

Compare Source

Patch Changes

• #​2229 d2b4b83 - Move ts-patch from peer to dependencies as it is required for typescript-transform-paths which is a dependency

v4.0.0

Compare Source

Major Changes

• #​2209 396d81e - Fix bundler v3 unintended breaking change: CSS imports not including layer info.

  In bundler v3 rollup-plugin-postcss is replaced with rollup-plugin-styler, in bundler v4 postcss-import is used instead of rollup-postcss-styler default import logic.

v3.0.1

Compare Source

Patch Changes

• #​2193 0a56fec - Specify correct assetFileNames convention for tailwind config too [name][extname]

v3.0.0

Compare Source

Major Changes

• #​2148 28f5a96 - Replace rollup-plugin-postcss with rollup-plugin-styler

  This is mostly a drop in replacement for rollup-plugin-postcss with a few minor changes

  1. We now explicitly default the name of the file to be [name][extname] this was the behaviour that the last plugin enforced but the new one needs to set it in the output config.

  You can override this by passing in the assetFileNames property in your rollupConfig e.g.

  rollupConfig({
    assetFileNames: "[name]-[hash][extname]"
  });
  

  This will apply the same asset file naming pattern to both CJS and ESM builds. 2. Your postcss.config.js will need to move from strings for the plugins to require statements

  Instead of:
  
  module.exports = {
    plugins: {
      "@​tailwindcss/postcss": {},
    },
  };
  
  It should be:
  
  module.exports = {
    plugins: [require("@​tailwindcss/postcss")],
  };
  
  For plugins that require configuration, pass the config object to the require statement:
  
  module.exports = {
    plugins: [
      require("autoprefixer")({ browsers: ["last 2 versions"] }),
      require("cssnano")({ preset: "default" })
    ],
  };
  

  2. All @​tailwind statement must convert to @​import statements as per tailwind v3 official guide on using postcss-import. @​tailwind is also deprecated in tailwind v4.

  @​tailwind base;
  @​tailwind components;
  @​tailwind utilities;
  

  @​import "tailwindcss/base";
  @​import "tailwindcss/components";
  @​import "tailwindcss/utilities";
  

Minor Changes

• #​2171 5dda9c9 - Fixed a rollup error when allowJS is set to true.

  RollupError: [plugin typescript] @​rollup/plugin-typescript: Path of Typescript compiler option 'outDir' must be located inside Rollup 'dir' option.
  

Patch Changes

• #​2095 0cdad73 - Bump rollup and plugin versions.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[cultureamp-renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 9 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
packages/components                      |  WARN  deprecated @types/[email protected]
packages/components                      |  WARN  deprecated [email protected]
Progress: resolved 111, reused 0, downloaded 0, added 0
Progress: resolved 170, reused 0, downloaded 0, added 0
Progress: resolved 430, reused 0, downloaded 0, added 0
Progress: resolved 465, reused 0, downloaded 0, added 0
Progress: resolved 568, reused 0, downloaded 0, added 0
Progress: resolved 774, reused 0, downloaded 0, added 0
Progress: resolved 1043, reused 0, downloaded 0, added 0
Progress: resolved 1172, reused 0, downloaded 0, added 0
Progress: resolved 1189, reused 0, downloaded 0, added 0
Progress: resolved 1200, reused 0, downloaded 0, added 0
Progress: resolved 1316, reused 0, downloaded 0, added 0
Progress: resolved 1439, reused 0, downloaded 0, added 0
Progress: resolved 1594, reused 0, downloaded 0, added 0
Progress: resolved 1653, reused 0, downloaded 0, added 0
Progress: resolved 1858, reused 0, downloaded 0, added 0
Progress: resolved 2039, reused 0, downloaded 0, added 0
packages/components                      |  WARN  deprecated [email protected]
Progress: resolved 2157, reused 0, downloaded 0, added 0
 ERR_PNPM_UNUSED_PATCH  The following patches were not used: rollup-plugin-postcss

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ed00048

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR