Webpack Compilation error when trying to run a ORM library inside Cypress test.

[miguel-mach-eight]

I have a complex app with many models and objects interacting in my back-end. I wanted to implement Factory pattern functions to easily build objects and sets of objects that exist inside my Cypress tests. To do so I wanted to implement a third party ORM library inside Cypress such as Sequelize or MikroORM. While trying to import and initialize one of my models' factory function inside a test, I get the following error:

Error: Webpack Compilation Error
./node_modules/@mikro-orm/core/utils/RequestContext.js
Module not found: Error: Can't resolve 'async_hooks' in 'C:\Users\Vongo\Documents\MACHEIGHT\NOMAD\e2e_testing\node_modules\@mikro-orm\core\utils'
resolve 'async_hooks' in 'C:\Users\Vongo\Documents\MACHEIGHT\NOMAD\e2e_testing\node_modules\@mikro-orm\core\utils'
  Parsed request is a module
  using description file: C:\Users\Vongo\Documents\MACHEIGHT\NOMAD\e2e_testing\node_modules\@mikro-orm\core\package.json (relative path: ./utils)
    Field 'browser' doesn't contain a valid alias configuration
    Looked for and couldn't find the file at the following paths:
  ...
 @ ./node_modules/@mikro-orm/core/utils/RequestContext.js 4:22-44
 @ ./node_modules/@mikro-orm/core/utils/index.js
 @ ./node_modules/@mikro-orm/core/index.js
 @ ./node_modules/@mikro-orm/core/index.mjs
 @ ./mikro-orm/orm.ts
 @ ./cypress/e2e/2. Data Buyer/test.cy.ts
 
    at Watching.handle [as handler] (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\@packages\server\node_modules\@cypress\webpack-preprocessor\dist\index.js:231:23)
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\webpack\lib\Watching.js:99:9
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\tapable\lib\Hook.js:154:20)
    at Watching._done (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\webpack\lib\Watching.js:98:28)
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\webpack\lib\Watching.js:73:19
    at Compiler.emitRecords (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\webpack\lib\Compiler.js:499:39)
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\webpack\lib\Watching.js:54:20
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\webpack\lib\Compiler.js:485:14
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\tapable\lib\Hook.js:154:20)
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\webpack\lib\Compiler.js:482:27
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\neo-async\async.js:2818:7
    at done (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\neo-async\async.js:3522:9)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\tapable\lib\Hook.js:154:20)
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\webpack\lib\Compiler.js:464:33
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\@packages\server\node_modules\graceful-fs\graceful-fs.js:143:16
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\@packages\server\node_modules\graceful-fs\graceful-fs.js:143:16
    at C:\Users\Vongo\AppData\Local\Cypress\Cache\12.3.0\Cypress\resources\app\node_modules\@packages\server\node_modules\graceful-fs\graceful-fs.js:61:14
    at FSReqCallback.oncomplete (node:fs:197:23)

This error happens with a MikroORM implementation that successfully connects to the DB and can create objects in a testing shell outside of Cypress. The Cypress test simply looks like this:

import { MasterOrganizationFactory } from "../../../mikro-orm/factories";
import { orm } from "../../../mikro-orm/orm";
describe('Factory tests', () => {

  it('creates a new master Organization', async () => {
    // Create an instance of a Master Organization
    await new MasterOrganizationFactory(orm).createOne();
  });

I'm aware that node-like code pertaining to the ORM libraries should be run in setUpNodeEvents, but I don't see a reason as to why it cannot be run inside tests.

[sharpius]

I faced a similar issue in our company when trying to implement ORM-like functionality in Cypress tests. After some exploration, we decided to shift away from using full-fledged ORM libraries like MikroORM within Cypress due to the complexities introduced by browser vs. Node.js environments. Instead, we adopted a SQL query builder library—specifically, Kysely—as our solution.

In our setup, the query-building logic resides on the browser side, allowing us to construct queries as objects. These queries are then serialized and sent to the Cypress back-end, where they are compiled and executed. This approach separates the concerns of query construction and execution, avoiding environment compatibility issues like the one you're encountering.

This method worked well for us because it provided a clean way to dynamically generate and execute queries in tests without the need for ORM-related dependencies that aren't browser-compatible. You might want to explore a similar architecture for your Cypress tests.

If you’d like, I can give you more details about solution.

[rasob]

I emailed you. Your solution sounds very interesting, but I don't really know how to implement it.