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 Could not resolve "badfilename" doesn't exit back to terminal #390

Closed
jgentes opened this issue Feb 4, 2022 · 1 comment · Fixed by #455 or #407
Closed

🐛 BUG: Error Could not resolve "badfilename" doesn't exit back to terminal #390

jgentes opened this issue Feb 4, 2022 · 1 comment · Fixed by #455 or #407
Assignees

Comments

@jgentes
Copy link
Contributor

jgentes commented Feb 4, 2022

What version of Wrangler are you using?

alpha

What operating system are you using?

WSL (Ubuntu 20)

Describe the Bug

Do wrangler dev badfilename which results in Error Could not resolve "badfilename" but it doesn't exit back to the terminal so you can try again. You have to CTRL-C out or X then you can restart wrangler.

@jgentes jgentes added the bug label Feb 4, 2022
@Electroid Electroid added this to the 2.0 milestone Feb 4, 2022
@Electroid
Copy link
Contributor

Electroid commented Feb 4, 2022

I think this is one of those esbuild errors that should bail, if it's running for the first time. But if this happens during the session, we can probably keep it going.

Edit: Alternatively, should all esbuild errors cause a bail when the session has not started yet?

threepointone added a commit that referenced this issue Feb 12, 2022
This adds an error when we use an entry point that doesn't exist, either for `wrangler dev` or `wrangler publish`, and either via cli arg or `build.upload.main` in `wrangler.toml`.  By using a common abstraction for `dev` and `publish`, This also adds support for using `build.config.main`/`build.config.dir` for `wrangler dev`.

Fixes #418
Fixes #390
threepointone added a commit that referenced this issue Feb 12, 2022
This adds an error when we use an entry point that doesn't exist, either for `wrangler dev` or `wrangler publish`, and either via cli arg or `build.upload.main` in `wrangler.toml`. By using a common abstraction for `dev` and `publish`, This also adds support for using `build.config.main`/`build.config.dir` for `wrangler dev`.

- Fixes #418
- Fixes #390
threepointone added a commit that referenced this issue Feb 13, 2022
This adds an error when we use an entry point that doesn't exist, either for `wrangler dev` or `wrangler publish`, and either via cli arg or `build.upload.main` in `wrangler.toml`. By using a common abstraction for `dev` and `publish`, This also adds support for using `build.config.main`/`build.config.dir` for `wrangler dev`.

- Fixes #418
- Fixes #390
threepointone added a commit that referenced this issue Feb 13, 2022
This adds an error when we use an entry point that doesn't exist, either for `wrangler dev` or `wrangler publish`, and either via cli arg or `build.upload.main` in `wrangler.toml`. By using a common abstraction for `dev` and `publish`, This also adds support for using `build.config.main`/`build.config.dir` for `wrangler dev`.

- Fixes #418
- Fixes #390
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
3 participants