Skip to content

Conversation

@oxo-fi-fi
Copy link
Contributor

What?

Adds port option to stencil start.

Why?

Our company manages multiple dev servers that each run on a unique port using config.stencil.port. It has become challenging to work efficiently on localhost as we need to track different ports. This way, when closing a tab or browser, we won't have to copy the URL or restart the dev server with stencil start -o again.

cc @bigcommerce/storefront-team

}

// Use initial (before updates) port for BrowserSync
const browserSyncPort = initialStencilConfig.port;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can do instead

Suggested change
const browserSyncPort = initialStencilConfig.port;
const browserSyncPort = cliOptions.port || initialStencilConfig.port;

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

then we need do change

const updatedStencilConfig = this.updateStencilConfig(
            { initialStencilConfig, port: browserSyncPort},
            storeInfoFromAPI,
);

@jairo-bc
Copy link
Contributor

@onur-o7 do you mind to rebase this one as well?

@jairo-bc
Copy link
Contributor

@jairo-bc jairo-bc closed this Jul 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants