feat: Prepare change needed for latest mdn-browser-compat-data format #196
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.
Commits
Description
Currently this repo is taking data from
"mdn-browser-compat-data"
atv5.4.5
, which is released on Dec 7, 2023 for like a year ago. I think catching up with the latest versionv5.6.6
is needed.Unfortunately between these two versions, there is a huge change on the build json. All the rules and types jsons are no longer partitioned into various sub-json file. Instead, they are now all living in one single
build/data.json
.To cope with this change, I have made some code changes to make
npm run update
run-able.You may want to actually checkout my branch, review the change, and run
npm run update
yourself to see if anything goes wrong.Please help review the change. It would be nice to see it can get released soon so that all the other upstream packages can consume the latest typing.