Description
I investigated an issue reported by a user during application migration.
After reviewing the installed package contents, I confirmed that the distributed @infragistics/ignite-ui-full package still contains legacy imports to jquery-ui/ui/core inside:
en/js/infragistics.core.js
en/js/infragistics.lob.js
Example from the installed package:
define([
"jquery",
"jquery-ui",
"jquery-ui/ui/core",
...
], factory)
This causes the application to fail when using jquery-ui 1.14.x, because jQuery UI 1.14 removed the deprecated ui/core.js module: https://jqueryui.com/changelog/1.14.0/.
This appears to be a package-level compatibility issue in the distributed Ignite UI bundle rather than an application-code issue.
- ignite-ui version: >19
- browser: N/A
Steps to reproduce
- Create application that depends on
@infragistics/ignite-ui-full
- Install:
@infragistics/ignite-ui-full@25.1.2
jquery-ui@1.14.1
- Start the application with
npm start
- Review the build output
- Inspect:
node_modules/@infragistics/ignite-ui-full/en/js/infragistics.core.js
node_modules/@infragistics/ignite-ui-full/en/js/infragistics.lob.js
Result
The build fails because the package tries to resolve the removed legacy path jquery-ui/ui/core.
The user-facing error is equivalent to:
Can't resolve 'jquery-ui/ui/core'
The distributed Ignite UI files still contain direct references to that path.
Expected result
@infragistics/ignite-ui-full 25.1.2 should not reference removed jQuery UI legacy module paths when used with jquery-ui 1.14.x.
If jQuery UI 1.14.x is supported, the distributed package should be updated so it no longer imports jquery-ui/ui/core.
Attachments
Relevant findings from the installed package:
-
en/js/infragistics.core.js
- contains AMD dependency on
jquery-ui/ui/core
-
en/js/infragistics.lob.js
- contains AMD dependency on
jquery-ui/ui/core
Temporary workaround identified:
- use
jquery-ui 1.13.3, which still contains the legacy module structure expected by the current package, until this issue is resolved
Description
I investigated an issue reported by a user during application migration.
After reviewing the installed package contents, I confirmed that the distributed
@infragistics/ignite-ui-fullpackage still contains legacy imports tojquery-ui/ui/coreinside:en/js/infragistics.core.jsen/js/infragistics.lob.jsExample from the installed package:
This causes the application to fail when using
jquery-ui 1.14.x, because jQuery UI 1.14 removed the deprecatedui/core.jsmodule: https://jqueryui.com/changelog/1.14.0/.This appears to be a package-level compatibility issue in the distributed Ignite UI bundle rather than an application-code issue.
Steps to reproduce
@infragistics/ignite-ui-full@infragistics/ignite-ui-full@25.1.2jquery-ui@1.14.1npm startnode_modules/@infragistics/ignite-ui-full/en/js/infragistics.core.jsnode_modules/@infragistics/ignite-ui-full/en/js/infragistics.lob.jsResult
The build fails because the package tries to resolve the removed legacy path
jquery-ui/ui/core.The user-facing error is equivalent to:
Can't resolve 'jquery-ui/ui/core'The distributed Ignite UI files still contain direct references to that path.
Expected result
@infragistics/ignite-ui-full 25.1.2should not reference removed jQuery UI legacy module paths when used withjquery-ui 1.14.x.If jQuery UI 1.14.x is supported, the distributed package should be updated so it no longer imports
jquery-ui/ui/core.Attachments
Relevant findings from the installed package:
en/js/infragistics.core.jsjquery-ui/ui/coreen/js/infragistics.lob.jsjquery-ui/ui/coreTemporary workaround identified:
jquery-ui 1.13.3, which still contains the legacy module structure expected by the current package, until this issue is resolved