TypeScript Compilation Errors: 'Uint8Array' is Not Generic in uuid Package

[Sn0w3y]

Description

Description

When attempting to build the Angular project, the TypeScript compiler fails due to incorrect usage of Uint8Array in the type definitions of the uuid package. The errors indicate that Uint8Array is being treated as a generic type, which is invalid in TypeScript.

---

Error Details

× Failed to compile.
✔ Browser application bundle generation complete.

66 unchanged chunks

Build at: 2025-01-08T06:28:30.993Z - Hash: c915a44ab19f3024 - Time: 6673ms

Error: node_modules/uuid/dist/cjs/parse.d.ts:1:39 - error TS2315: Type ‘Uint8Array’ is not generic.

1 declare function parse(uuid: string): Uint8Array;
                                       ~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/uuid/dist/cjs/v35.d.ts:2:53 - error TS2315: Type ‘Uint8Array’ is not generic.

2 export declare function stringToBytes(str: string): Uint8Array;
                                                   ~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/uuid/dist/cjs/v35.d.ts:6:166 - error TS2315: Type ‘Uint8Array’ is not generic.

6 export default function v35(version: 0x30 | 0x50, hash: HashFunction, value: string | Uint8Array, namespace: UUIDTypes, buf?: Uint8Array, offset?: number): string | Uint8Array;

                                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~

× Failed to compile.

---

Expected Behavior

The Angular project should compile successfully without TypeScript errors related to the uuid package, resulting in a build output in the specified www directory.

---

Environment

• Operating System: Windows
• Node.js Version: Node20
• TypeScript Version: 5.6.3
• Angular Version: v19
• uuid Package Versions:
  • [email protected] via [email protected]
  • [email protected] via [email protected]
  • [email protected] directly in the project

---

Additional Information

• Deprecated Packages Warnings:

  • Multiple deprecated packages are being used, such as [email protected], [email protected], [email protected], [email protected], @xmldom/[email protected], [email protected], and [email protected] & 3.0.2.

• Potential Conflicts:

  • Multiple versions of the uuid package might be causing type definition conflicts.

• Temporary Workaround Applied:

  • Added "skipLibCheck": true to tsconfig.json to bypass type checking of declaration files, allowing the build to proceed.

---

Possible Solutions Attempted

1. Skipped Library Type Checking:

   • Modified tsconfig.json to include:

     {
       "compilerOptions": {
         // ... other options ...
         "skipLibCheck": true
       }
     }

   • Result: Build succeeded without TypeScript errors, but this masks underlying type issues.

2. Attempted to Align uuid Package Versions:

   • Considered using the overrides field in package.json to force a single uuid version.
   • Challenges: Potential incompatibilities with dependencies expecting different uuid versions.

3. Explored Updating or Patching Affected Packages:

   • Identified that [email protected] and [email protected] depend on older uuid versions.
   • Next Steps: Check for updates to these packages or consider patching their dependencies.

---

References

• npm Package: [uuid on npm](https://www.npmjs.com/package/uuid)
• TypeScript Error TS2315: [TypeScript Handbook - Error Messages](https://www.typescriptlang.org/docs/handbook/compiler-options.html)
• Angular Build Documentation: [Angular CLI - ng build](https://angular.io/cli/build)

See here:

uuidjs/uuid#856

Screenshots

No response

Operating System

No response

How to reproduce the Error?

Steps to Reproduce

1. Clone the Repository:

   git clone https://github.com/OpenEMS/OpenEMS.git
   cd OpenEMS/ui

2. Clean Install Dependencies:

   rm -rf node_modules package-lock.json
   npm cache clean --force
   npm install --legacy-peer-deps

3. Run Build:

   npx ng build -c "openems,openems-backend-prod,prod" --output-path=www

[sfeilmeier]

Is this with current develop; I saw this only here yesterday: #2957

[Sn0w3y]

I can not get it to work - no matter what i do npm always uses 11.0.4 - i guess it is not in the develop branch - you're right !

[Sn0w3y]

@sfeilmeier fixed in 11.0.5 FYI

uuidjs/uuid@24ac2fd