Tracking issue - Any issues related to the use of Node v14

[derrickmehaffy]

Node v14 tracking issue

This issue will be used to note any issues related to supporting the next LTS version for node. If you notice anything please post it here. Any other issues created will be closed, locked, and linked to this issue.

Please note that Node v14 will not be supported until it's actual LTS release date which you can find on: https://nodejs.org/en/about/releases/

Template for reporting a bug

Please copy and paste the following markdown template, and fill it out.

- OS: 
- Node Version: 
- NPM Version: 
- Yarn (optional): 

### When did you encounter the issue

Example: during project creation, build process, when I uploaded a file, ect

### Link to issue project on GitHub or exact steps to reproduce

Where possible please test in fresh projects, and push those projects to a temporary GitHub repo.

[imaksp]

• OS: MAC 10.15.6
• Node Version: 14.6.0
• NPM Version: NA
• Yarn (optional): 1.22.5
• Database (added) : MongoDB (as this is related to mongodb driver)

When did you encounter the issue

Just start project using yarn develop & see warnings as shown below:
(Use node --trace-warnings ... to show where the warning was created)
(node:53784) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
(node:53784) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
(node:53784) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency

Context

Its due to bug in mongodb driver see: https://jira.mongodb.org/browse/NODE-2536
This is already fixed in version mongodb version 3.5.7+, but strapi has locked mongoose version to 5.8.0 which depends on older mongodb driver (3.3.5), I have made pull request for updating mongoose but tests are failing
See pull: #7859, another pull from bot: #7916
tests are failing because blank username is not allowed now (error Invalid empty username provided) See this mongoose issue: Automattic/mongoose#8640

[imaksp]

• OS: Mac 10.15.6
• Node Version: 12.18.4/14.6.0
• NPM Version:
• Yarn (optional): 1.22.5
• Strapi: 3.1.5

When did you encounter the issue

Got following warnings while installing/updating (yarn install) strapi using Node 12.8.4, it seems to be related to Node 14
warning strapi-admin > webpack-dev-server > chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
warning strapi-admin > webpack-dev-server > chokidar > fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

[derrickmehaffy]

DMehaffy's Node v14 checking of tests:

Linux Desktop

Using:

• Linux Mint 20

Tests

• SQLite
• MySQL 8
• MariaDB 10.5
• PostgreSQL 13
• MongoDB 4.4

Linux Server

Using:

• Ubuntu Server 20.04
• Ubuntu Server 18.04
• CentOS 8
• RHEL 8.2

Tests

• SQLite
• MySQL 8
• MariaDB 10.5
• PostgreSQL 13
• MongoDB 4.4

Windows

Using:

• Windows 10
• Windows Server 2019

Tests

• SQLite
• MySQL 8
• MariaDB 10.5
• PostgreSQL 13
• MongoDB 4.4

MacOS

Using:

• MacOS Catalina

Tests

• SQLite
• MySQL 8
• MariaDB 10.5
• PostgreSQL 13
• MongoDB 4.4

Notes

Only issue found was if npm/yarn is able to determine and properly install the sharp requirements from their prebuilt binaries, if either determines the requirement need to be compiled from source on demand, issue can arise from missing dependencies (mainly build related stuff such as python3, gc, ect).

The issue doesn't appear to be with Strapi directly but the users system and installed packages. A key point of note is during the Node install on Windows, there an option to check a box to install these dependencies via chocolatey, if this isn't selected by the user sharp install fails. I believe most of the node 14 issues are user based and not Strapi based.

Mac and Linux saw no issues other than ARM based systems which are upstream problems and not ours, workarounds exist and this should only be a problem for development reasons as most users are not deploying production instances onto ARM CPUs (other than say a Raspberry PI, but that is a hobbyist method)

[lauriejim]

This issue has been mentioned on Strapi Community. There might be relevant details there:

https://forum.strapi.io/t/first-installation-issues/364/2

[derrickmehaffy]

Related to the above listed issues:
#7921 (comment) => @soupette have we updated that dependency?

No I haven't but the admin panel is building correctly and the dev mode is still available/working in both the monorepo and a generated app.

[derrickmehaffy]

@alexandrebodin @Convly @petersg83

As Soupette has confirmed the frontend side, do you feel we need anything else from this?

[alexandrebodin]

We can keep it open until node 14 becomes the LTS version in case we get uninteded issues