Skip to content

chore(deps)(deps): bump @nestjs/schedule from 6.1.3 to 12.0.1 - #190

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/nestjs/schedule-12.0.1
Closed

chore(deps)(deps): bump @nestjs/schedule from 6.1.3 to 12.0.1#190
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/nestjs/schedule-12.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Contributor

Bumps @nestjs/schedule from 6.1.3 to 12.0.1.

Release notes

Sourced from @​nestjs/schedule's releases.

Release 12.0.1

What's Changed

Full Changelog: nestjs/schedule@12.0.0...12.0.1

Release 12.0.0

What's Changed

@nestjs/schedule is now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 7.x — 6.1.3 goes straight to 12.0.0).

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts / index.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root.

// ✅
import { ScheduleModule, Cron, CronExpression } from '@nestjs/schedule';
// ❌ no longer resolvable
import { CronExpression } from '@​nestjs/schedule/dist/enums/cron-expression.enum';

Only . and ./package.json are exported.

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, a CommonJS app can keep doing:

const { ScheduleModule } = require('@nestjs/schedule');

This is why the package now declares "engines": { "node": ">=20.19.0" }require(esm) is unflagged from Node 20.19 / 22.12 onward. On older Node versions the require will throw ERR_REQUIRE_ESM.

Fixes

  • Duplicate scheduler names are now rejected at startup. Two @Cron, @Interval, or @Timeout declarations sharing an explicit name previously slipped past decorator collection and only conflicted later; the DUPLICATE_SCHEDULER error is now thrown during initialization, where you can actually see it.

Upgrading

npm i @nestjs/schedule@12
  • Node 20.19+ (or 22.12+) is required.
  • Replace any deep imports with root imports.
  • If you were importing from the removed root index.js shim path explicitly, drop the path — @nestjs/schedule resolves on its own.
Commits
  • 1df146c chore(): release v12.0.1
  • 7c241a5 Merge pull request #2349 from nestjs/feat/export-schedule-explorer
  • 00d3db8 feat: export ScheduleExplorer from the package entry point
  • 55e94dd Merge pull request #2347 from nestjs/renovate/cimg-node-24.x
  • 7e5d551 Merge pull request #2348 from nestjs/renovate/nest-monorepo
  • 5237ab0 chore(deps): update nest monorepo to v12.0.1
  • 6bd6e14 chore(): release v12.0.0
  • 6719285 feat: support nestjs v12
  • 3bcca07 chore(deps): update node.js to v24.20.0
  • 1b24bb7 chore(deps): update nest monorepo to v11.2.3 (#2346)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Aug 31, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: npm. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/nestjs/schedule-12.0.1 branch from ed02cf9 to 2745286 Compare August 31, 2026 07:30
Bumps [@nestjs/schedule](https://github.com/nestjs/schedule) from 6.1.3 to 12.0.1.
- [Release notes](https://github.com/nestjs/schedule/releases)
- [Commits](nestjs/schedule@6.1.3...12.0.1)

---
updated-dependencies:
- dependency-name: "@nestjs/schedule"
  dependency-version: 12.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/nestjs/schedule-12.0.1 branch from 2745286 to 1afcb01 Compare September 1, 2026 10:51
ihabkhaled added a commit that referenced this pull request Sep 1, 2026
Coordinated bump of @nestjs/common, core, platform-express, testing,
schedule, mongoose and schematics to their v12 releases across all 18
NestJS services and the 4 shared packages that depend on them (closing
dependabot PRs #188, #190, #193, #196, which each only bumped one
package and left the tree in a broken mixed-version state).

NestJS 12's common/core/testing packages ship as pure ESM with no
CommonJS build, which this repo's TypeScript config (Node16 module
resolution) rejects outright. Verified empirically that the minimal,
non-invasive fix is `module: esnext` + `moduleResolution: bundler` in
each workspace's tsconfig — TypeScript stops requiring extensions on
relative imports (avoiding a rewrite of every import in the codebase),
while `"type": "module"` in package.json makes Node's own ESM loader
handle the compiled output correctly. tsc-alias's -f flag adds the
`.js` extensions to compiled output that Node's loader still needs.

Knock-on fixes, each proven with an actual boot (not just a green
typecheck):

- Prisma's generated client is copied into dist/, not compiled by tsc;
  a new tools/typescript/copy-generated-prisma.mjs step runs between
  the compile and the tsc-alias pass so the copy exists before
  tsc-alias resolves the extension on that import.
- Auth-service and routing-service's plain-node Prisma seed scripts
  (seed.js and friends, using require()) are renamed .cjs, since a
  parent "type": "module" makes Node parse a bare .js as ESM.
  prisma.config.ts and the seed/seed:permissions package.json scripts
  updated to match.
- Jest keeps running as CommonJS (switching it to ESM breaks the
  `jest.mock`/`jest.fn` globals in every spec file) but needs
  @nestjs/*'s compiled JS transformed back to CJS for tests only,
  via a babel-jest pass scoped to node_modules/@nestjs plus a
  reflect-metadata setupFile (v12 no longer pulls it in as a side
  effect). @babel/core is pinned to the stable v7 line, not v8 --
  babel-plugin-transform-import-meta's v8-only release conflicts with
  this repo's other Babel 7 consumers.
- nestjs-pino bumped 4.6.1 -> 5.0.0 (only version whose peer range
  allows @nestjs/common v12).
- @nestjs/throttler has not yet published a v12-compatible peer range
  (latest is 6.5.0, capped at ^11); Docker's from-scratch dependency
  install (no lockfile, unlike CI's `npm ci`) needs --legacy-peer-deps
  to accept that known-safe mismatch, added to every service's
  Dockerfile and Dockerfile.dev.

Verified end-to-end, not just gated: typecheck, lint, build and test
green across all 18 services and 6 shared packages, and a real `docker
build` + `docker run` of claw-health-service reaches "Nest application
successfully started" inside the actual production image.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

Looks like @nestjs/schedule is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Sep 1, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/nestjs/schedule-12.0.1 branch September 1, 2026 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants