💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

Hi @akieboyegodgift02! Excellent root-cause writeup. For developers hitting this exact combination (NestJS 12 ESM + TypeORM + Jest), here is a concise reference for the configuration adjustments:

1. Jest ESM Configuration with NestJS 12

Nest 12 packages are published as pure ES modules. To make Jest parse them without CommonJS syntax errors:
In jest.config.ts:

import type { Config } from 'jest';

const config: Config = {
  preset: 'ts-jest/presets/default-esm',
  testEnvironment: 'node',
  extensionsToTreatAsEsm: ['.ts'],
  moduleNameMapper: {
    '^(\.{1,2}/.*)\.js$': '$1',
  },
  transform: {
    '^.+\.(t|j)sx?$': [
      'ts-jest',
      {
        useESM: true,
      },
    ],
  },
};

export default config;

And execute your test runner with Node's experimental VM modules enabled:

"scripts": {
  "test": "node --experimental-vm-modules node_modules/jest/bin/jest.js"
}

2. TypeORM Driver for SQLite

As of recent TypeORM releases, the legacy sqlite driver is deprecated in favor of better-sqlite3:

npm install better-sqlite3
npm install -D @types/better-sqlite3

In your test TypeOrmModule.forRoot config:

TypeOrmModule.forRoot({
  type: 'better-sqlite3',
  database: ':memory:',
  entities: [User, Wallet, Transaction],
  synchronize: true,
})

3. Circular Entity Relations

When entities reference each other (e.g. User ↔ Wallet ↔ Transaction), use arrow functions for relation targets and TypeScript import type to prevent circular evaluation during module bootstrap:

import type { Wallet } from './wallet.entity.js';

@Entity()
export class User {
  @OneToMany(() => Wallet, (wallet) => wallet.user)
  wallets: Wallet[];
}

Hey there! 👋

Thanks for posting in the GitHub Community, @akieboyegodgift02 ! You are more likely to get a useful response if you are posting in the applicable category. The Apps, API and Webhooks category is a place for our community to discuss and provide feedback GitHub's APIs and webhooks. GitHub provides two APIs: a REST API and a GraphQL API. Webhooks allow you to build or set up integrations, such as GitHub Apps or OAuth Apps, which subscribe to certain events on GitHub.com

I've gone ahead and moved this to the correct category for you. Good luck!