🐛 BUG: Error Could not resolve "badfilename" doesn't exit back to terminal #390
Assignees
Comments
|
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
Repository owner
moved this from Must-have
to Done
in workers-sdk
Feb 13, 2022
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
Merged
This was referenced Feb 10, 2024
This was referenced Feb 17, 2024
This was referenced Feb 28, 2024
This was referenced Mar 7, 2024
This was referenced Mar 15, 2024
This was referenced Mar 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of
Wranglerare you using?alpha
What operating system are you using?
WSL (Ubuntu 20)
Describe the Bug
Do
wrangler dev badfilenamewhich results inError 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.The text was updated successfully, but these errors were encountered: