Skip to content

Conversation

@camillobruni
Copy link
Contributor

We moved the params parsing partially to the Params which was not use in cli.js
Directly use the cli-only arguments in cli.js instead.

@netlify
Copy link

netlify bot commented Jan 20, 2026

Deploy Preview for webkit-jetstream-preview ready!

Name Link
🔨 Latest commit ac9185a
🔍 Latest deploy log https://app.netlify.com/projects/webkit-jetstream-preview/deploys/696fb025df73990008c5eb90
😎 Deploy Preview https://deploy-preview-266--webkit-jetstream-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@camillobruni camillobruni requested a review from danleh January 20, 2026 16:41
@camillobruni
Copy link
Contributor Author

As a follow-up I should still implement a proper cli tests that parses the output for --dump-test-list and --help

Copy link
Contributor

@danleh danleh left a comment

Choose a reason for hiding this comment

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

LGTM with question / optional rejection of the startsWith('--no') change.

}
let value = parts.slice(1).join("=");
if (flagName === "no-prefetch") value = "false";
if (flagName.startsWith("no-")) value = "false";
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we have some other parameter that uses this --no prefix? Or rather: all other boolean parameters are set to false by default, whereas prefetchResources is true, right? So maybe don't generify this just yet, since supplying, e.g., --no-ramification does nothing, right?

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