Skip to content

chore(deps): update fs-extra to 11.3.6 across all packages#328

Open
X-Guardian wants to merge 3 commits into
open-constructs:mainfrom
X-Guardian:chore/bump-fs-extra
Open

chore(deps): update fs-extra to 11.3.6 across all packages#328
X-Guardian wants to merge 3 commits into
open-constructs:mainfrom
X-Guardian:chore/bump-fs-extra

Conversation

@X-Guardian

@X-Guardian X-Guardian commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Description

Bumps fs-extra to 11.3.6 (and @types/fs-extra to 11.0.4) in every package that depends on it, so the whole monorepo resolves a single copy of each.

Before this change the versions were inconsistent: five packages were already on the 11.x line (11.3.4 / ^11.3.0), while three — @cdktn/provider-generator, @cdktn/cli-core, and cdktn-cli — plus the standalone test/ harness were still pinned to fs-extra@8.1.0 / @types/fs-extra@8.1.5. This aligns all of them on the current release.

Packages updated:

Package fs-extra @types/fs-extra
@cdktn/provider-generator 8.1.011.3.6 8.1.511.0.4
@cdktn/cli-core 8.1.011.3.6 8.1.511.0.4
cdktn-cli 8.1.011.3.6 8.1.511.0.4
test/ (non-workspace) ^8.1.0^11.3.6 ^8.1.5^11.0.4
@cdktn/provider-schema 11.3.411.3.6 11.0.4 (unchanged)
@cdktn/commons 11.3.411.3.6 11.0.4 (unchanged)
@cdktn/hcl2cdk 11.3.411.3.6 11.0.4 (unchanged)
@cdktn/hcl2json 11.3.411.3.6 11.0.4 (unchanged)
@cdktn/hcl-tools ^11.3.0^11.3.6 11.0.4 (unchanged)

Two source changes were required. The three packages crossing the 8.x11.x boundary were checked against the fs-extra breaking changes in that window. The @types/fs-extra@11 typings are stricter than @types/fs-extra@8 and flagged two existing calls that passed a recursive option to a copy — fs.copy/fs.copySync are always recursive, so recursive was never a valid CopyOptions/CopyOptionsSync key; the looser v8 typings silently accepted it. Removing it is a no-op at runtime:

  • @cdktn/provider-generator/src/get/constructs-maker.tserror TS2769 on fs.copy(source, target, { recursive: true, overwrite: false })fs.copy(source, target, { overwrite: false }).
  • cdktn-cli/src/bin/cmds/helper/init.tserror TS2353 on fs.copySync(src, dest, { recursive: true })fs.copySync(src, dest).

No behavioural change was needed for the other differences. move() defaulting to overwrite: false from v9 onward doesn't affect the three fs.move call sites in the same file, which already pass { overwrite: true } explicitly. Every other method used across these packages (existsSync, readFile(Sync), writeFile(Sync), remove(Sync), pathExists, mkdirp/mkdirs, copy(Sync), stat, readJson(Sync), appendFileSync, rmSync, unlinkSync, accessSync, constants) is unchanged from 8 through 11. The rest of the 8→11 range only dropped support for Node.js < 14, which the repo already requires.

Checklist

  • I have updated the PR title to match CDKTN's style guide
  • I have run the linter on my code locally
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation if applicable
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works if applicable
  • New and existing unit tests pass locally with my changes

@X-Guardian X-Guardian force-pushed the chore/bump-fs-extra branch from 2b38d2f to 7b67260 Compare July 13, 2026 14:05
@X-Guardian X-Guardian marked this pull request as ready for review July 13, 2026 14:34
@X-Guardian X-Guardian requested a review from a team as a code owner July 13, 2026 14:34
@X-Guardian X-Guardian force-pushed the chore/bump-fs-extra branch from 7b67260 to d8f238d Compare July 14, 2026 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant