KendoReact licensing when using scripts instead of webpack

[Andrew]

I have an existing web application where I'm trying to introduce new functionality using React and KendoReact. I am using npm but not webpack.

I can successfully load the scripts per the instructions (both from the CDN as shown, and from the npm packages using the versions in the dist/cdn directories).

However, it's complaining about the license not being activated:

Progress KendoReact
kendo-react-intl.js:1 License activation failed for @progress/kendo-react-intl
No license found.
See https://www.telerik.com/kendo-react-ui/my-license/?utm_medium=product&utm_source=kendoreact&utm_campaign=kendo-ui-react-purchase-license-keys-warning for more information.

The Dojo examples on the instruction page exhibit this behavior too.

I've installed and activated the kendo-licensing package per the instructions, and included the now-licensed dist/index.js script in my page before any other KendoReact scripts. I still get the licensing error, though.

Is there any way to license an application that's only using prebuilt scripts?

[Stefan]

Hello, Andrew,

This is a known case and the team is currently working on finding the best approach to resolve it.

I will follow up as soon as we have official information on this.

Regards,
Stefan
Progress Telerik

[Stefan]

Hello, Andrew,

We have logged an item in GitHub where we will share any progress on the task:

https://github.com/telerik/kendo-react/issues/859

Apologies for any inconvenience this may has caused you.

Regards,
Stefan
Progress Telerik

[Andrew]

Thank you!

[Jaime]

I have the same problem, is there a solution?

[Stefan]

Hello, Jaime,

The team is still working on a solution and testing different alternatives.

I will add your report to the issue as well.

Regards,
Stefan
Progress Telerik

[Jaime]

What is the recommendation in this case, because we need the kendo components for new features that go to the client, at some point due to the license we will be out of order?

[Stefan]

I have escalated this to the management team for an official statement. Please have in mind that this week there are Easter holidays plus a national holiday and many people are out of the office. This means that the official answer may be delayed for a couple of days.

Apologies for the created inconvenience.

[Pieter]

I have a scenario where all the Kendo React packages are added to the webpack externals and all the files are loaded via the CDN with systemJS (resulting in the same messages as above). Are these kinds of scenarios also considered?

Are there any know work-arounds available (apart from not adding it to the externals)?

 

Apart from that: I would expect a big message to the "Using with Scripts" section, since that functionality is not really usable.

[Stefan]

Hello, Pieter,

Yes, the webpack externals are also considered as it also uses the CDNs.

Currently, there is no workaround using KendoReact after version 4 with CDN for production builds. This is why the team is looking at this with high priority to introduce a way to validate the license in those cases.

All managers are informed and this is escalated.

Regards,
Stefan
Progress Telerik

[Stefan]

Hello,

This is the official statement from our side about this case. We want to apologize for the created situation and this is our recommendation until it is resolved.

At this time we are actively working towards ensuring that folks using KendoReact and Kendo UI through the minified bundle and our CDN, but this is a bit more complicated compared to what has been done for the npm packages. An unfortunate side-effect of this is that the warning message will still appear in your scenario. As you have reached out to ensure that you can be compliant with our licensing we know that you are not attempting to abuse our licensing system and can, for the time being, ignore this message. This message will only be displayed in the console of your browser and will not be something that your average end-user will see since they rarely browse with the developer console open.

We completely understand that this is not ideal, but we do not want to hold any application releases because of this.

Regards,
Stefan
Progress Telerik

[Pieter]

Any updates on this issue?

[Stefan]

This is already in the final stages of testing. You can check a preview here:

https://www.telerik.com/kendo-react-ui-develop/components/installation/scripts-only/ (3. Add your Script License key.)

[Pieter]

Great to see a solution :) Since it's in final testing, is there any ETA? Will it be in 4.8.0?

[Stefan]

Yes, this is correct. It will be available in part of 4.8.0. It is already part of the 4.8.0 dev version.

The ETA of version 4.8.0 can vary as it induces other functionalities as well that need to be tested.

[Pieter]

I was trying to test this the other day, but couldn't get it to work, is it supposed to be working already (with the kendo-licensing@1.2.0 and the rest @4.8.0-dev)?

[Stefan]

As this is still in the dev version, I can recommend waiting for the official version 4.8.0 to ensure that everything is cleared. We are expecting the new version next week or a little after that.

[Pieter]

I can wait, but isn't feedback (before release) about the scenarios customers critical for this change?

[Stefan]

Yes, the feedback is always very helpful for us.

As the script license key requires posting a script tag with your personal key, I can suggest opening a private ticket where we can check what is causing the issue.

I made a test with my key and it was working as expected.

[Pieter]

I opened a ticket for this, I couldn't get it to work with webpack externals. Is there already an example made which works with webpack externals and loading the files from a CDN?

[Stefan]

Thank you for opening the ticket. I will check it out.