Remove support for deprecated YAML and .es6 config files (#1752)#1752
Closed
robhogan wants to merge 1 commit into
Closed
Remove support for deprecated YAML and .es6 config files (#1752)#1752robhogan wants to merge 1 commit into
.es6 config files (#1752)#1752robhogan wants to merge 1 commit into
Conversation
meta-cla
Bot
added
the
CLA Signed
meta-codesync
Bot
changed the title
.es6 config files.es6 config files (#1752)
meta-codesync Bot
pushed a commit
that referenced
this pull request
Jun 28, 2026
Summary: These have been deprecated (with a runtime warning) and removal planned for a year now. I believe they're little used in the wild and inherently very limited. Expo has already dropped support. Removing YAML support lets us drop a dependency also. Changelog: ``` - **[Breaking]**: Remove support for YAML and `.es6` config files ``` Differential Revision: D109987702
meta-codesync
Bot
force-pushed
the
export-D109987702
branch
from
2c49ba9 to
8c77b51
Compare
Summary: These have been deprecated (with a runtime warning) and removal planned for a year now. I believe they're little used in the wild and inherently very limited. Expo has already dropped support. Removing YAML support lets us drop a dependency also. Changelog: ``` - **[Breaking]**: Remove support for YAML and `.es6` config files ``` Differential Revision: D109987702
meta-codesync
Bot
force-pushed
the
export-D109987702
branch
2 times, most recently
from
a3d075c to
f4976e5
Compare
Contributor
|
@robhogan has exported this pull request. If you are a Meta employee, you can view the originating Diff in D109987702. |
Contributor
|
This pull request has been merged in 8c772a3. |
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
1 participant
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:
These have been deprecated (with a runtime warning) and removal planned for a year now. I believe they're little used in the wild and inherently very limited. Expo has already dropped support.
Removing YAML support lets us drop a dependency also.
Changelog:
Differential Revision: D109987702