https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • g
    What is the priority of this. It would seem to me that Node support is very important especially for Enterprise customers like oursleves
  • g
    For us to be able to take full advantage of Workers we would need to accomplish a full shift from Lambda for all of our companies
  • i
    Did I read something there for future but not active yet...? I'm pretty sure that on the Spectrum entitlements that come back from the API on the Dash you see Workers. I expect them to work already on Spectrum sources done via the HTTP(S) pipelines, so that would be Workers for TCP, right?
  • i
    Copy code
    "spectrum": {
  "argo_smart_routing": false,
  "byoip": false,
  "enabled": true,
  "ftp": false,
  "ipv4_quota": 10,
  "payg": false,
  "subscribed": true,
  "udp": true,
  "workers": false
}
  • i
    Here there are some interesting items @User... 😛 Actors?! Cloudflare Pages? Live Tailing, that would be cool!
    Copy code
    "workers": {
  "actors": false,
  "appworker_develop": false,
  "cloudflare_pages": false,
  "enabled": true,
  "live_tailing": false,
  "request_cpu_ms": 30000,
  "same_zone_worker_on_subrequest": false,
  "scheduled": false,
  "script_limit_exception": 30,
  "scripts": 1000,
  "text_binding_size_limit_exception": 1024,
  "use_pipeline": false
}
  • a
    Haha yeah, when those things get released, will let this channel know :). Also Actors is Durable Objects - internally we called them Actor Workers for a while before the name change.
  • c
    What is appworker_develop
  • a
    I think that's for the Cloudflare App Store - which the Workers team doesn't currently support.
  • c
    What about cloudflare pages
  • i
    Yeah, it should be what @User mentioned, I seem to recall.
  • i
    No sneak peaks...? I will find out, I'm the reigning Community MVP champion for finding out the "Weeks" of announcement. I got all last year, this year they just told me before ahah
  • a
    Cloudflare Pages will be a product to make deploying static sites extremely easy 🙂
  • i
    I like that.
  • k
  • g
    That's the one!
  • g
    @albert-zhao When is Node support slated?
  • i
    I believe he mentioned initial support early next year.
  • a
    That's an interesting idea! Curious, how would it be useful for you if we could raise the subrequest limit?
  • g
    I wonder if I could run GraphQL and Node code and move everything to Workers
  • g
    @kristian This would basically replace AWS AppSync right?
  • g
    Because we would be hosting our own GraphQL services at that point correct?
  • k
    yep, exactly
  • k
    it has good support for writing your own resolvers (so you can take incoming queries and get corresponding database info, etc.) as well as good defaults for apollo's data sources (https://www.apollographql.com/docs/apollo-server/data/data-sources/)
  • k
    i'm not 100% up to date on what all appsync does tho
  • c
    @albert-zhao I’m an advanced certificate manager customer. I am interested in having support for this. Can you pass my feedback to the right team? https://scotthelme.co.uk/introducing-another-free-ca-as-an-alternative-to-lets-encrypt/
  • a
    ooo yeah I replied to you in an earlier thread: "We're looking into early next year at Node module support - will probably start with a subset of common Node APIs, such as HTTP, Crypto, and Buffer. Historically our engineers focused on Browser APIs because of their long-term compatibility. For Node, we may need to ask users what version they need us to be compatible with."
  • g
    Can we currently use NPM?
  • a
    O very cool! Yeah let me send it to their chatroom
  • c
    Yes but many packages are broken due to the limited Node API support
  • g
    @albert-zhao Q1 Node support?
1...567...2509Latest