Skip to content
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

🐛 BUG: "[ERROR] Cannot infer host from first route: undefined." with Wrangler 3.30.1 #5146

Open
Razzmatazzz opened this issue Mar 3, 2024 · 1 comment
Labels
bug Something that isn't working needs reproduction Needs reproduction from OP regression Break in existing functionality as a result of a recent change

Comments

@Razzmatazzz
Copy link

Which Cloudflare product(s) does this pertain to?

Wrangler core

What version(s) of the tool(s) are you using?

3.30.1 [Wrangler]

What version of Node are you using?

20.11.0

What operating system and version are you using?

Windows 11

Describe the Bug

Observed behavior

When using Wrangler 3.30.1 and attempting to start the worker with wrangler dev, I get the following error:

X [ERROR] Cannot infer host from first route: undefined.

  You can explicitly set the `dev.host` configuration in your wrangler.toml file, for example:

        
        [dev]
        host = "example.com"

This error does not occur if I'm using Wrangler 3.30.0 or lower.

Expected behavior

Since the changelog does not indicate any kind of breaking change, I would expect future versions to continue working.

Steps to reproduce

The error is occurring in this repo: https://github.com/the-hideout/tarkov-api

Please provide a link to a minimal reproduction

https://github.com/the-hideout/tarkov-api

Please provide any relevant error logs

No response

@Razzmatazzz Razzmatazzz added the bug Something that isn't working label Mar 3, 2024
@Razzmatazzz Razzmatazzz changed the title 🐛 BUG: [ERROR] Cannot infer host from first route: undefined. with 3.30.1 🐛 BUG: "[ERROR] Cannot infer host from first route: undefined." with Wrangler 3.30.1 Mar 3, 2024
@penalosa penalosa added the regression Break in existing functionality as a result of a recent change label Aug 19, 2024
@andyjessop
Copy link
Contributor

@Razzmatazzz I'm just looking at this now, but I can't reproduce it with the example you provided. Would it be possible to get a minimal reproduction, so that we can isolate the issue?

@andyjessop andyjessop added the needs reproduction Needs reproduction from OP label Oct 7, 2024
@andyjessop andyjessop removed their assignment Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that isn't working needs reproduction Needs reproduction from OP regression Break in existing functionality as a result of a recent change
Projects
Status: Untriaged
Development

No branches or pull requests

3 participants