Webpack 5 ModeFederation error when shared package version is not in semver

Bug report

What is the current behavior? One of our packages has version ‘dev’ set in package.json as it is internal not released yet package.

....
"dependencies": {
    "{PACKAGE_NAME}": "dev",
}
....

When I try to configure ModeFederationPlugin for our main app I configure shared modules as follows:

const packageJson = require('../package.json');

const packageName = packageJson.name;
const packageDeps = packageJson.dependencies;

new ModuleFederationPlugin({
   ....
    shared: {
      ...packageDeps,
      react: {
        singleton: true,
        eager: true,
        requiredVersion: packageDeps.react,
      },
      'react-dom': {
        singleton: true,
        eager: true,
        requiredVersion: packageDeps['react-dom'],
      },
    },
    ....
  }),

When I run webpack it gives me next error:

ERROR in resolving fallback for shared module ($PACKAGE_NAME}
Module not found: Error: Can't resolve 'dev' in '{PATH_TO_FILE_USING_PACKAGE}'

If the current behavior is a bug, please provide the steps to reproduce.

1. Add package with version different from semantic versioning standard to dependencies of the project
2. Try to add ModuleFederationPlugin to the webpack config of the app with the following config:

const packageJson = require('../package.json');

const packageName = packageJson.name;
const packageDeps = packageJson.dependencies;

new ModuleFederationPlugin({
    name: packageName,
    remotes: {},
    shared: {
      ...packageDeps,
      angular: {
        singleton: true,
        eager: true,
        requiredVersion: packageDeps.angular,
      },
      react: {
        singleton: true,
        eager: true,
        requiredVersion: packageDeps.react,
      },
      'react-dom': {
        singleton: true,
        eager: true,
        requiredVersion: packageDeps['react-dom'],
      },
    },
  }),

1. Run webpack and see the errors in the console

What is the expected behavior? I assume that if webpack can resolve node_modules with non-semantic versioning then ConsumeSharedPlugin should also be able to

If any additional info is needed for me, please let me know

Other relevant information: webpack version: 5.24.4 Node.js version: v14.15.0 Operating System: macOS Catalina Version 10.15.7 Additional tools:

[alexander-akait]

We have logic to detect singleton problems with multiple versions, so each package should have valid (parsable by semver) version

[webpack-bot]

Issue was closed because of inactivity.

If you think this is still a valid issue, please file a new issue with additional information.