[Telerik and Kendo UI Licensing] Error while importing license.

1 Answer 9 Views
Licensing
Yuri
Top achievements
Rank 1
Yuri asked on 15 Sep 2025, 09:40 AM | edited on 15 Sep 2025, 11:26 AM
Hi, we have made an update of Angular version (to 19) alongside Kendo. It was working fine two weeks ago, but now we started having the following problem:
npm error [INFO][Telerik and Kendo UI Licensing] Telerik and Kendo UI License Key found at: /vercel/path0/telerik-license.txt
npm error License issued at 9/26/2023, 8:20:20 AM to XXXXX
npm error TypeError: glob[_0xb5a829(...)] is not a function
npm error     at setRuntimeLicense (/vercel/path0/node_modules/@progress/kendo-licensing/bin/kendo-ui-license.js:2:47328)
npm error     at main (/vercel/path0/node_modules/@progress/kendo-licensing/bin/kendo-ui-license.js:2:65092)
npm error     at async /vercel/path0/node_modules/@progress/kendo-licensing/bin/kendo-ui-license.js:2:77506
npm error [ERROR][Telerik and Kendo UI Licensing] Error while importing license.
We use:
"@progress/kendo-angular-buttons": "^19.2.0",
"@progress/kendo-angular-charts": "^19.2.0",
"@progress/kendo-angular-common": "^19.2.0",
"@progress/kendo-angular-dateinputs": "^19.2.0",
"@progress/kendo-angular-dialog": "^19.2.0",
"@progress/kendo-angular-dropdowns": "^19.2.0",
"@progress/kendo-angular-excel-export": "^19.2.0",
"@progress/kendo-angular-gauges": "^19.2.0",
"@progress/kendo-angular-grid": "^19.2.0",
"@progress/kendo-angular-icons": "^19.2.0",
"@progress/kendo-angular-indicators": "^19.2.0",
"@progress/kendo-angular-inputs": "^19.2.0",
"@progress/kendo-angular-intl": "^19.2.0",
"@progress/kendo-angular-l10n": "^19.2.0",
"@progress/kendo-angular-label": "^19.2.0",
"@progress/kendo-angular-layout": "^19.2.0",
"@progress/kendo-angular-listview": "^19.2.0",
"@progress/kendo-angular-menu": "^19.2.0",
"@progress/kendo-angular-navigation": "^19.2.0",
"@progress/kendo-angular-pager": "^19.2.0",
"@progress/kendo-angular-pdf-export": "^19.2.0",
"@progress/kendo-angular-pdfviewer": "^19.2.0",
"@progress/kendo-angular-popup": "^19.2.0",
"@progress/kendo-angular-progressbar": "^19.2.0",
"@progress/kendo-angular-spreadsheet": "^19.2.0",
"@progress/kendo-angular-toolbar": "^19.2.0",
"@progress/kendo-angular-tooltip": "^19.2.0",
"@progress/kendo-angular-treelist": "^19.2.0",
"@progress/kendo-angular-treeview": "^19.2.0",
"@progress/kendo-angular-upload": "^19.2.0",
"@progress/kendo-angular-utils": "^19.2.0",
"@progress/kendo-data-query": "^1.7.0",
"@progress/kendo-drawing": "^1.20.1",
"@progress/kendo-font-icons": "^4.5.0",
"@progress/kendo-licensing": "^1.7.1",
I didn't find anything related to this issue on the FAQ pages. Can I get some help and support about this issue?

1 Answer, 1 is accepted

Sort by
0
Accepted
Martin Bechev
Telerik team
answered on 16 Sep 2025, 08:31 AM

Hello Yuri,

Based on the error message and your current setup, the issue is related to the glob package. It usually happens because of version mismatches - some packages expect the old glob API (pre-v10), where glob(...) was a function, but the latest glob (v10+) is ESM-only and exports differently.

Since v1.5.2 of the @progress/kendo-licensing package, glob is a dependency at version ^10.0.0.

Consider downgrading the @progress/kendo-licensing (v1.5.1) or if you want to keep @progress/kendo-licensing@1.7.1, you can force your project to use a compatible version. glob:

For npm 8+:

"overrides": { "glob": "8.1.0" }

For yarn:

"resolutions": { "glob": "8.1.0" }

Then run npm install.

As a side note, the account from which this ticket was opened doesn't have an assigned valid license. Please contact your license holder to be able to open private tickets with a shorter response time.

    Regards,


    Martin Bechev
    Progress Telerik

    Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

    Yuri
    Top achievements
    Rank 1
    commented on 16 Sep 2025, 09:04 AM

    Hi Martin,

    Thank you so very much for the reply, indeed it was a problem with version mismatching. The actual problem was happening because of a cache in our CD pipeline. After tweaking the script a bit, it worked as expected!

    And you're right, I'm not the holder of the license, but we double checked with the license holder and it should be valid until next year.

    Nonetheless, thank you so very much for the response.

    Best regards,
    Yuri Lyra
    Martin Bechev
    Telerik team
    commented on 16 Sep 2025, 11:00 AM

    Hi Yuri,

    Glad to hear that this helped.

    Regards,

    Martin

    Tags
    Licensing
    Asked by
    Yuri
    Top achievements
    Rank 1
    Answers by
    Martin Bechev
    Telerik team
    Share this question
    or