-
Notifications
You must be signed in to change notification settings - Fork 365
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
The netlify CLI attempts to access the network despite the --offline option #5015
Comments
@swiing I'm not able to reproduce this. I've attached the output I'm getting below. Is the repository you're working on public? (If yes, could you share it) Do you have any specific configuration in ncli dev --offline
◈ Netlify Dev ◈
◈ No app server detected. Using simple static server
◈ Unable to determine public folder to serve files from. Using current working directory
◈ Setup a netlify.toml file with a [dev] section to specify your dev server settings.
◈ See docs at: https://cli.netlify.com/netlify-dev#project-detection
◈ Running static server from "5051-redirect-us"
◈ Setting up local development server
────────────────────────────────────────────────────────────────
Netlify Build
────────────────────────────────────────────────────────────────
❯ Version
@netlify/build 27.18.3
❯ Flags
offline: true
❯ Current directory
/Users/kunal/Desktop/myfolder.nosync/oss/p-cli-test/5051-redirect-us
❯ Config file
/Users/kunal/Desktop/myfolder.nosync/oss/p-cli-test/5051-redirect-us/netlify.toml
❯ Context
dev
────────────────────────────────────────────────────────────────
1. Run command for local development
────────────────────────────────────────────────────────────────
◈ Static server listening to 3999
(dev.command completed in 2ms)
┌─────────────────────────────────────────────────┐
│ │
│ ◈ Server now ready on http://localhost:8888 │
│ │
└─────────────────────────────────────────────────┘ |
@jackiewmacharia Do you know how to reset the cache for the packages that the edge functions environment downloads? Would help me in reproducing the error faced by the user above. I was looking here: cli/src/lib/edge-functions/proxy.js Lines 163 to 179 in 138681d
But couldn't pin-point what to do to clear the cache so that I can receive the error message described in the issue.
|
This is an interesting one. On the one hand, it feels like we should respect |
@tinfoil-knight , my repo is not public, but I believe it is pretty "standard". My CLI version: netlify-cli/10.4.0 wsl-x64 node-v16.16.0 Ironically, I actually can't reproduce myself. I guess because I have everything in cache by now. |
Describe the bug
Documentation for the dev command says that the option 'offline (boolean) - disables any features that require network access'.
However, this seems inaccurate wrt edge function environment.
Running
netlify dev --offline
when the network connectivity is not available starts ok, but eventually throws.Steps to reproduce
1- cut network connectivity.
2- run
npx netlify dev --offline
and then the CLI throws.
Configuration
No response
Environment
System:
OS: Linux 5.10 Ubuntu 20.04 LTS (Focal Fossa)
CPU: (12) x64 AMD Ryzen 5 PRO 5650U with Radeon Graphics
Memory: 3.26 GB / 5.65 GB
Container: Yes
Shell: 5.0.16 - /bin/bash
Binaries:
Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
The text was updated successfully, but these errors were encountered: