Strange SyntaxError in MongoDB after upgrading Mongoose to v7

[JamesJansson]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the bug has not already been reported

Mongoose version

7.0.2

Node.js version

18.13.0

MongoDB server version

5.1.0

Typescript version (if applicable)

4.8.4

Description

Issue after upgrading to Mongoose V7. In the MongoDB library

SyntaxError: Invalid or unexpected token

The toke is ?. which makes no sense since ?. operator appears to be normal and has worked in much younger versions of node.

Multiple reports appear on stack overflow, with the only recommendation being "downgrade to v6":
https://stackoverflow.com/questions/75681631/why-node-js-gives-this-error-from-the-npm-modules
https://stackoverflow.com/questions/75675925/syntax-and-database-connection-error-in-node-js

Steps to Reproduce

Upgraded from v5 to v7 (any version 7). I have no MongoDB installed through package.json (only installed courtesy of Mongoose) After building in TS, running the server using nodemon, I get the following error:

Stack trace:

node_modules/mongodb/lib/collection.js:70
            pkFactory: db.options?.pkFactory ?? utils_1.DEFAULT_PK_FACTORY,
                                  ^
SyntaxError: Invalid or unexpected token
    at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)

I'm working in Ubuntu 22.04.2

Downgrading to v6 doesn't have this problem.

Expected Behavior

No response

[vkarpov15]

Can you please double check your Node.js version using node -v? This should only be an issue if you're running on Node.js 12 or older.

If you are indeed on Node.js 18, can you please provide your tsconfig.json? Could be a build step issue.

[ronenteva]

Same issue here, node.js v18

[vkarpov15]

@ronenteva your comment is not very helpful. Please provide more detailed instructions on how to repro this issue.

[ronenteva]

@vkarpov15 I'm sorry, I still couldn't find exactly how to reproduce the issue, but I'm pretty sure it has something to do with esm installed.

[vkarpov15]

We'll try out with esm. But just a thought - why do you need an esm bundler if Node.js supports esm natively?

[ronenteva]

I use it for older projects, so I can have both require and import

[zhe1ka]

i can confirm that the issue is appeared when using esm like this
require = require('esm')(module, { cjs: true }); module.exports = require('./app.js');
fixed by:

1. removed esm
2. added "type": "module" to package.json
3. changed all require with import; i suppose module.exports => export (default) requires too.
4. all url of imported modules should be with an extension (ie .js)

[vkarpov15]

Confirmed this is a known issue in esm: standard-things/esm#918 (comment) . Also standard-things/esm#909. TLDR; esm hasn't been maintained in some time, doesn't work with more recent additions to the JavaScript language spec.

You would need to use a fork of esm, like esm-wallaby.