Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 9, 2026

closes #16717

npm install fails when igniteui-webcomponents@6.4.0 is present due to conflicting marked peer dependency versions. igniteui-angular requires ^16.3.0 while igniteui-webcomponents@6.4.0 uses 17.x.

Changes

  • Updated marked peer dependency from ^16.3.0 to >=16.3.0 in projects/igniteui-angular/package.json

This allows compatibility with both current (16.x) and future versions of marked used by igniteui-webcomponents. Since marked is already an optional peer dependency, applications retain control over version pinning if needed.

Original prompt

This section details on the original issue you should resolve

<issue_title>Application fails to build due to mismatching dependency versions</issue_title>
<issue_description>## Description
Look at the attached sample. Try to build the app. The following error occur.

Image
  • igniteui-angular version: 21.0.0

Result

The app can't install node modules due to mismatching dependency versions

Attachments

Attach a sample if available, and screenshots, if applicable.

NavigationalTabs_angular-standalone (2).zip</issue_description>

Comments on the Issue (you are @copilot in this section)

@Lipata In the project `package.json`, there are the following peer dependencies:
"igniteui-webcomponents": "^6.3.0",
"marked": "^16.3.0",

In the latest igniteui-webcomponents package, version 6.4.0, the marked package version is 17.x,, and on npm i the different version of the marked package cannot be resolved, even though the igniteui-webcomponents package is marked as optional:

        "igniteui-webcomponents": {
          "optional": true
        },

There are the following solutions:

  • define "igniteui-webcomponents": "~6.3.0", which means igniteui-angular package will be restricted to use only versions before 6.4.0, which is not recommended.
  • remove dependency of marked in the peerDependencies and use igniteui-webcomponents exposed logic for that in the code. This should be done in both igniteui-angular and igniteui-webcomponents repos. @damyanpetev, @rkaraivanov.
  • do not restrict "makred" version in the peerDependencies, so that it can always match the version in the igniteui-webocomponents:
"marked": ">=16.3.0",

The latest suggestion can be applied for now, for the following branches: 20.1.x, 21.0x and master


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: Lipata <2621802+Lipata@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix application build failure due to mismatching dependency versions Fix peer dependency conflict with marked package Jan 9, 2026
Copilot AI requested a review from Lipata January 9, 2026 13:30
@Lipata Lipata added version: 21.1.x dependencies Pull requests that update a dependency file labels Jan 9, 2026
@Lipata Lipata marked this pull request as ready for review January 9, 2026 13:32
@Lipata Lipata changed the title Fix peer dependency conflict with marked package fix: resolve peer dependency conflict with marked package Jan 9, 2026
@Lipata Lipata changed the title fix: resolve peer dependency conflict with marked package fix(*): resolve peer dependency conflict with marked package Jan 9, 2026
@Lipata Lipata merged commit 945c14b into master Jan 12, 2026
7 of 9 checks passed
@Lipata Lipata deleted the copilot/fix-dependency-version-issues branch January 12, 2026 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file version: 21.1.x

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Application fails to build due to mismatching dependency versions

3 participants