fix: invalid frontend-platform import in Footer.jsx #398
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.
I am working on some experimental changes to improve frontend-platform, and when modernizing the
package.json
exports
field, I started seeing this error in the course authoring MFE:According to the
frontend-platform documentation
, configuration functions likeensureConfig
should always be imported from@edx/frontend-platform
, not@edx/frontend-platform/config
which is actually a "private" implementation file.Currently, frontend-platform's package.json uses a legacy syntax that lets you import from any files you want within it, but when we modernize it to use the
exports
field to define the set of public exports,/config
will presumably no longer work since it's not part of the public API.So far, this is the only bad import I've found.