Files
formipay/node_modules/chrome-launcher/contributing.md
dwindown e8fbfb14c1 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>
2026-04-18 17:02:14 +07:00

559 B

Release Procedure

  1. When good, do npm publish. it'll run the prepublish script (build & test)
    • complete publishing to npm. (we now have the tagged commit, too).
  2. To complete the changelog: Do git log --oneline and then edit the resulting text to match the style in changelog.md. it's pretty manual. update that file. commit.
  3. Push back up to origin. Do git push --tags to ensure the tag is there.
  4. Open up https://github.com/GoogleChrome/chrome-launcher/releases and Draft a New Release. Use the same changelog.md markdown. Publish.