https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • s
    or I mean the storage gets reset
  • h
    Depending on how long you wait
  • h
    Yes
  • s
    okay this doesn't work I can't run wrangler twice apparently
  • s
    Error: connect ECONNREFUSED 127.0.0.1:61914
  • h
    Not on the same code
  • s
    no not same code
  • s
    two terminals in two directories
  • s
    tried doing 
    npx wrangler dev --local
  • s
    worked on first one but got the error above on the second one
  • s
  • s
    maybe I can use 
    SCRIPT
    instead? but I am not sure where to even specify that
  • s
    okay got it working with 
    npx wrangler dev --local --inspector-port 61915
  • s
    I feel like I run into areas where the docs need updating on a daily basis. I should probably be hired to update them at this point 😛
  • s
    if you run locally more than once it tries binding to the same debug ports and fails
  • s
    on Windows at least
  • s
    It should realise it's taken and pick another one 🤔
  • s
    yeah that did happen for the port it bound the worker too but not the debugger
  • s
    hmm now when I fetch from the bound worker I get a 500
  • s
    it doesn't seem to connect to the worker itself
  • s
    oh wait one sec
  • s
    nvm that part was my fault. but the port issue is real 😛
  • s
    Interesting, probably a good idea to make an issue for that if there's not one already
  • s
    > "services" fields are experimental and may change or break at any time.
  • s
    oh this is also not mentioned in the docs (at least on this page https://developers.cloudflare.com/workers/platform/bindings/about-service-bindings/)
  • k
    I have no idea why that warning is there
  • k
    Service Bindings have been GA for awhile now iirc
  • u
    Where do you even see that text?
  • s
    wrangler
  • s
    and I think I just found another bug
1...228122822283...2509Latest