-
Notifications
You must be signed in to change notification settings - Fork 352
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
Wrong repo is being loaded in netlify dev #629
Comments
Running latest version of Netlify CLI, v2.21.0 |
Apologies, this seems to be an issue with nuxt. |
This was referenced Oct 13, 2021
This was referenced Feb 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
- Do you want to request a feature or report a bug?
Report a bug
- What is the current behavior?
When switching between two repos in different local directories, I'm getting what seems to be the cached version of the other. (When I run
netlify dev
in repo-1's directory, repo-2 is showing in the browser). Of course, I've cleared browser cache, of course, and tried in multiple browsers, but still the wrong repo is loading.- If the current behavior is a bug, please provide the steps to reproduce.
Above.
- What is the expected behavior?
Should load the correct project : )
- Local Environment Information
──────────────────────┐
Current Netlify User │
──────────────────────┘
Email: brendan@pachira.site
Teams:
pachiraDIG's team: Collaborator
────────────────────┐
Environment Info │
────────────────────┘
System:
OS: Linux 4.4 Ubuntu 18.04.2 LTS (Bionic Beaver)
CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
Binaries:
Node: 11.13.0 - ~/.nvm/versions/node/v11.13.0/bin/node
Yarn: 1.15.2 - /usr/bin/yarn
npm: 6.9.0 - ~/.nvm/versions/node/v11.13.0/bin/npm
────────────────────┐
Netlify Site Info │
────────────────────┘
Current site: clartecafe
Netlify TOML: /c/pachira/clarte/netlify.toml
Admin URL: https://app.netlify.com/sites/clartecafe
Site URL: https://clartecafe.com
Site Id: cb5c9c20-a43d-4ed1-830b-065a28af4a21
The text was updated successfully, but these errors were encountered: