Repository navigation
Rebuild the form bundle without direct eval - #128
Merged
Merged
Conversation
Statamic 6.35 compares field conditions without eval, but the published bundle was built before that and still warned when sites bundled it.
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.
Summary
Statamic 6.35 compares field conditions without
eval. Our publishedform.jswas built before that, so bundling it still triggered Rolldown's directevalwarning.This rebuilds
form.jsagainst the current checker and passes the field handle toshowField, which that version requires.lodash-esis a dev dependency because the checker imports it at build time. Sites do not need to upgrade Statamic.Test plan
form.jswith Vite 8 and confirm the directevalwarning is gone