-
Notifications
You must be signed in to change notification settings - Fork 747
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
cache some calls in node_modules/.cache
(specifically - account selection, but maybe more)
#300
Closed
Tracked by
#12
Labels
maintenance
Maintenance task
Comments
Assigning to myself so I remember to bring this up in our team meeting |
Added to the agenda. |
Unassigning now that we discussed it. |
threepointone
added a commit
that referenced
this issue
Jul 3, 2022
This adds caching for account id fetch/selection for all wrangler commands. Currently, if we have an api/ouath token, but haven't provided an account id, we fetch account information from cloudflare. If a user has just one account id, we automatically choose that. If there are more than one, then we show a dropdown and ask the user to pick one. This is convenient, and lets the user not have to specify their account id when starting a project. However, if does make startup slow, since it has to do that fetch every time. It's also annoying for folks with multiple account ids because they have to pick their account id every time. So we now cache the account_id into `node_modules/.cache/wrangler` (much like pages already does with account id and project name). This patch also refactors `config-cache.ts`; it only caches if there's a `node_modules` folder, and it looks for the closest node_modules folder (and not directly in cwd). I also added tests for when a `node_modules` folder isn't available. It also trims the message that we log to terminal. Closes #300
threepointone
added a commit
that referenced
this issue
Jul 3, 2022
This adds caching for account id fetch/selection for all wrangler commands. Currently, if we have an api/ouath token, but haven't provided an account id, we fetch account information from cloudflare. If a user has just one account id, we automatically choose that. If there are more than one, then we show a dropdown and ask the user to pick one. This is convenient, and lets the user not have to specify their account id when starting a project. However, if does make startup slow, since it has to do that fetch every time. It's also annoying for folks with multiple account ids because they have to pick their account id every time. So we now cache the account_id into `node_modules/.cache/wrangler` (much like pages already does with account id and project name). This patch also refactors `config-cache.ts`; it only caches if there's a `node_modules` folder, and it looks for the closest node_modules folder (and not directly in cwd). I also added tests for when a `node_modules` folder isn't available. It also trims the message that we log to terminal. Closes #300
threepointone
added a commit
that referenced
this issue
Jul 3, 2022
This adds caching for account id fetch/selection for all wrangler commands. Currently, if we have an api/oauth token, but haven't provided an account id, we fetch account information from cloudflare. If a user has just one account id, we automatically choose that. If there are more than one, then we show a dropdown and ask the user to pick one. This is convenient, and lets the user not have to specify their account id when starting a project. However, if does make startup slow, since it has to do that fetch every time. It's also annoying for folks with multiple account ids because they have to pick their account id every time. So we now cache the account_id into `node_modules/.cache/wrangler` (much like pages already does with account id and project name). This patch also refactors `config-cache.ts`; it only caches if there's a `node_modules` folder, and it looks for the closest node_modules folder (and not directly in cwd). I also added tests for when a `node_modules` folder isn't available. It also trims the message that we log to terminal. Closes #300
threepointone
added a commit
that referenced
this issue
Jul 4, 2022
This adds caching for account id fetch/selection for all wrangler commands. Currently, if we have an api/oauth token, but haven't provided an account id, we fetch account information from cloudflare. If a user has just one account id, we automatically choose that. If there are more than one, then we show a dropdown and ask the user to pick one. This is convenient, and lets the user not have to specify their account id when starting a project. However, if does make startup slow, since it has to do that fetch every time. It's also annoying for folks with multiple account ids because they have to pick their account id every time. So we now cache the account_id into `node_modules/.cache/wrangler` (much like pages already does with account id and project name). This patch also refactors `config-cache.ts`; it only caches if there's a `node_modules` folder, and it looks for the closest node_modules folder (and not directly in cwd). I also added tests for when a `node_modules` folder isn't available. It also trims the message that we log to terminal. Closes #300
threepointone
added a commit
that referenced
this issue
Jul 4, 2022
This adds caching for account id fetch/selection for all wrangler commands. Currently, if we have an api/oauth token, but haven't provided an account id, we fetch account information from cloudflare. If a user has just one account id, we automatically choose that. If there are more than one, then we show a dropdown and ask the user to pick one. This is convenient, and lets the user not have to specify their account id when starting a project. However, if does make startup slow, since it has to do that fetch every time. It's also annoying for folks with multiple account ids because they have to pick their account id every time. So we now cache the account_id into `node_modules/.cache/wrangler` (much like pages already does with account id and project name). This patch also refactors `config-cache.ts`; it only caches if there's a `node_modules` folder, and it looks for the closest node_modules folder (and not directly in cwd). I also added tests for when a `node_modules` folder isn't available. It also trims the message that we log to terminal. Closes #300
threepointone
added a commit
that referenced
this issue
Jul 4, 2022
This adds caching for account id fetch/selection for all wrangler commands. Currently, if we have an api/oauth token, but haven't provided an account id, we fetch account information from cloudflare. If a user has just one account id, we automatically choose that. If there are more than one, then we show a dropdown and ask the user to pick one. This is convenient, and lets the user not have to specify their account id when starting a project. However, if does make startup slow, since it has to do that fetch every time. It's also annoying for folks with multiple account ids because they have to pick their account id every time. So we now cache the account details into `node_modules/.cache/wrangler` (much like pages already does with account id and project name). This patch also refactors `config-cache.ts`; it only caches if there's a `node_modules` folder, and it looks for the closest node_modules folder (and not directly in cwd). I also added tests for when a `node_modules` folder isn't available. It also trims the message that we log to terminal. Closes #300
threepointone
added a commit
that referenced
this issue
Jul 5, 2022
This adds caching for account id fetch/selection for all wrangler commands. Currently, if we have an api/oauth token, but haven't provided an account id, we fetch account information from cloudflare. If a user has just one account id, we automatically choose that. If there are more than one, then we show a dropdown and ask the user to pick one. This is convenient, and lets the user not have to specify their account id when starting a project. However, if does make startup slow, since it has to do that fetch every time. It's also annoying for folks with multiple account ids because they have to pick their account id every time. So we now cache the account details into `node_modules/.cache/wrangler` (much like pages already does with account id and project name). This patch also refactors `config-cache.ts`; it only caches if there's a `node_modules` folder, and it looks for the closest node_modules folder (and not directly in cwd). I also added tests for when a `node_modules` folder isn't available. It also trims the message that we log to terminal. Closes #300
threepointone
added a commit
that referenced
this issue
Jul 5, 2022
This adds caching for account id fetch/selection for all wrangler commands. Currently, if we have an api/oauth token, but haven't provided an account id, we fetch account information from cloudflare. If a user has just one account id, we automatically choose that. If there are more than one, then we show a dropdown and ask the user to pick one. This is convenient, and lets the user not have to specify their account id when starting a project. However, if does make startup slow, since it has to do that fetch every time. It's also annoying for folks with multiple account ids because they have to pick their account id every time. So we now cache the account details into `node_modules/.cache/wrangler` (much like pages already does with account id and project name). This patch also refactors `config-cache.ts`; it only caches if there's a `node_modules` folder, and it looks for the closest node_modules folder (and not directly in cwd). I also added tests for when a `node_modules` folder isn't available. It also trims the message that we log to terminal. Closes #300
Repository owner
moved this from In Progress
to Done
in workers-sdk
Jul 5, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: