Repository navigation
Support apexcharts 8 (v1.25.1) - #41
Merged
Merged
Conversation
Widen the optional apexcharts peer range to ^8.0.0 and develop against 8.4. Chart only uses new ApexCharts, render, updateOptions and destroy, which are unchanged in v8. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
apexchartspeer range widened to^4.5.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0; devDependency^8.4.0.Chartonly usesnew ApexCharts,render,updateOptions,destroy, unchanged in v8. Apps on 4–7 need no change.npm cifails on the current^7peer cap.Verified locally: verify:version, typecheck, lint (0 errors), build, Playwright 272/272.
After merge: tag
v1.25.1.🤖 Generated with Claude Code