Parcel is not compiling .mjs without filename

[MylesWardell]

🐛 bug report

Parcel is not compiling .mjs files when the file type is not directly declared by the import

.babelrc

{
  "plugins": [
    [
      "module-resolver",
      {
        "root": ["./src"],
        "alias": {
          "~": "./src"
        }
      }
    ]
  ]
}

🤔 Expected Behavior

This should compile

😯 Current Behavior

The compiler throws an error not recognising a valid mjs file

🔦 Context

I am trying to integrate with @Trulioo SDK which provides a unique way of installing their custom SDK. In the node modules (the worst place to throw an error) parcel complains that it does not recognise a .mjs file because it does not include the file type (.mjs)

💻 Code Sample

// How trulioo recommend to import their package 
const GlobalGatewayCapture = require('@trulioo/globalgateway-image-capture-sdk')

🌍 Your Environment

Software	Version(s)
Parcel	2.2.1
Node	16.13.2
npm	8.1.2
Operating System	Windows

[mischnic]

mjs is missing in this list:

parcel/packages/resolvers/default/src/DefaultResolver.js

Line 25 in 083e530

? ['ts', 'tsx', 'js', 'jsx', 'json']

I guess we should add it given that it's de-facto standardized by Node.

[MylesWardell]

Is their any short term solution I can use to get my current project up and running? Otherwise what would the ETA on a potential patch be?

I understand this is an open source project with limited available time, just trying to meet my teams requirements 👍

[danieltroger]

@MylesWardell this sounds like a case for yarn patch. With that you can basically have a patch references from your package.json that will automatically be applied for everyone running yarn install. Here I wrote about how to use a patch: DevExpress/testcafe#6624 (comment) and to generate it just do yarn patch <package>.

Dunno if you need yarn berry for it though.

[devongovett]

This was added in the last release. #8667