primefaces / primefaces/primereact

Version information missing in subpackages

Open
#8,065 0 comments 0 reactions 2 assignees View on GitHub

@tugcekucukoglu is already working on this.

Since Jun 3, 2025.

Type: Enhancement
Dominant language
CSS
Stars
8.3k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

I'm trying to use prime react together with module federation. This gives many warnings like the following if the prime react version isn't manually specified version in the module federation configuration:

[...]
WARNING in shared module C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\overlayservice\overlayservice.esm.js -> C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\overlayservice\overlayservice.esm.js
No version specified and unable to automatically determine one. No version in description file (usually package.json). Add version to description file C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\overlayservice\package.json, or manually specify version in shared config.

WARNING in shared module C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\portal\portal.esm.js -> C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\portal\portal.esm.js
No version specified and unable to automatically determine one. No version in description file (usually package.json). Add version to description file C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\portal\package.json, or manually specify version in shared config.     

WARNING in shared module C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\progressbar\progressbar.esm.js -> C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\progressbar\progressbar.esm.js
No version specified and unable to automatically determine one. No version in description file (usually package.json). Add version to description file C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\progressbar\package.json, or manually specify version in shared config.

WARNING in shared module C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\ripple\ripple.esm.js -> C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\ripple\ripple.esm.js
No version specified and unable to automatically determine one. No version in description file (usually package.json). Add version to description file C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\ripple\package.json, or manually specify version in shared config.     

WARNING in shared module C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\utils\utils.esm.js -> C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\utils\utils.esm.js
No version specified and unable to automatically determine one. No version in description file (usually package.json). Add version to description file C:\Users\mju\git\docbridge-central-2-plugin-resource-director\node_modules\primereact\utils\package.json, or manually specify version in shared config. 

Having the version in the generated package.jsons means that module federation can automatically determine the version.

Reproducer

No response

System Information
npmPackages:
primeReact: 10.9.6
Steps to reproduce the behavior

No response

Expected behavior

Expected package.json content, example for utils, but needed for all packages:

{
    "main": "./utils.cjs.js",
    "module": "./utils.esm.js",
    "unpkg": "./utils.min.js",
    "types": "./utils.d.ts",
    "sideEffects": false,
    "version": "10.9.6"
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.