fix: prevent asset conflicts between React and Grid.js versions

Add coexistence checks to all enqueue methods to prevent loading
both React and Grid.js assets simultaneously.

Changes:
- ReactAdmin.php: Only enqueue React assets when ?react=1
- Init.php: Skip Grid.js when React active on admin pages
- Form.php, Coupon.php, Access.php: Restore classic assets when ?react=0
- Customer.php, Product.php, License.php: Add coexistence checks

Now the toggle between Classic and React versions works correctly.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
dwindown
2026-04-18 17:02:14 +07:00
parent bd9cdac02e
commit e8fbfb14c1
74973 changed files with 6658406 additions and 71 deletions

View File

@@ -0,0 +1,45 @@
"use strict";
exports.__esModule = true;
exports.default = void 0;
/**
* Safari 10.3 had an issue where async arrow function expressions within any class method would throw.
* After an initial fix, any references to the instance via `this` within those methods would also throw.
* This is fixed by converting arrow functions in class methods into equivalent function expressions.
* @see https://bugs.webkit.org/show_bug.cgi?id=166879
*
* @example
* class X{ a(){ async () => {}; } } // throws
* class X{ a(){ async function() {}; } } // works
*
* @example
* class X{ a(){
* async () => this.a; // throws
* } }
* class X{ a(){
* var _this=this;
* async function() { return _this.a }; // works
* } }
*/
const OPTS = {
allowInsertArrow: false,
specCompliant: false
};
var _default = ({
types: t
}) => ({
name: "transform-async-arrows-in-class",
visitor: {
ArrowFunctionExpression(path) {
if (path.node.async && path.findParent(t.isClassMethod)) {
path.arrowFunctionToExpression(OPTS);
}
}
}
});
exports.default = _default;
module.exports = exports.default;