Totally broken with JQuery 3.5.x + Kendo-ui 2020.2.x

[robertmclaws]

Hello! Love this library, and have been using it for a long time in various projects. Wanted to let you know that JQuery 3.5 made some changes that appear to break the bindings. After upgrading JQuery on a previously working project, none of the Kendo controls show up anymore.

I'm not very familiar with the inner workings, and have already wasted a couple days trying to fix it, so I had to revert back to the prior release of JQuery to get back on track. But it would be really great if you could dig into it at some point and see if there's a way to fix it.

Thanks so much for this tool! It's been a huge help to my team.

[bmsmg]

I recently upgraded jQuery to 3.5.1 and ko-kendo works fine. Could you create a small sample project to reproduce your issue? One issue I noticed was the new(er) Kendo version has a module dependency on jQuery 3.4.x. This caused everything to appear broken. I assume due to breaking changes added in jQuery 3.5. The fix was to force-resolve that dependency to jQuery 3.5.1 (yarn: https://classic.yarnpkg.com/en/docs/selective-version-resolutions/, npm: https://www.npmjs.com/package/npm-force-resolutions)

[robertmclaws]

So, using the npm tool you suggested, I was able to narrow it down a little further. I'm able to get everything working by staying on the previous release of Kendo (2020.1.406), but redirecting all jQuery instances to 3.5.1.

However, when I upgraded to the 2020.2 releases of jQuery, anything tied to an Input control will not bind and render. I'm not sure if anything else broke, because I'm only using it for Sliders, ConboBoxes, and NumericInput controls at the moment. But something definitely changed in the latest Kendo + jQuery that prevents this triumvirate from working properly.

Update: This simple repro works fine: https://codepen.io/JediMasterRob/pen/LYpgKga

Seems like Webpack could potentially be the culprit here. Might a script registration order issue, or maybe I'm missing an alias. But when I downgrade, it works fine.

[bmsmg]

If you can put together a small webpack-enabled repo that exhibits the broken behavior I can help you out.

[CGollhardt]

Probably unrelated to this project, but I had nearly the same issue. I solved it via an alias (WebPack):

    resolve: {
        alias: {
            'jquery': path.join('path/to/node_modules', 'jquery/src/jquery')
        }
    },