-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sku v13: Remove old configuration values and CLI arguments #980
Conversation
🦋 Changeset detectedLatest commit: 56549d8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
a4ab669
to
8ae6ae9
Compare
const makeWebpackConfig = ({ | ||
isIntegration = false, | ||
port = 0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you clarify the removal of port
? Not immediately obvious from the diff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
port
isn't specified anywhere makeWebpackConfig
is called, and the only usage of it was in the now-deleted stringifyEnvarValues
. Eventually the value ends up in a define plugin for process.env.PORT
.
I don't think anyone is depending on process.env.PORT
inside their app code. A high-level look at a github search for process.env.PORT
aligns with that assumption.
Removing unused and deprecated config values and CLI args. See changesets for details.
Usage
--tenant
--env
--build
env
config. Not too concerned as the migration path should be straightforward.