Basically with Pages you would only pay

Basically, with Pages, you would only pay for serving the on-demand assets, all static asset requests would be free.
30 Replies
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
Hello, I’m Allie!
Yes, it would. Currently, accounts have a limit of 100k functions requests a day(only for the beta), which can be raised by the team in this server. Also, Functions are currently free too, while they are in beta.
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
Hello, I’m Allie!
Pricing is not 100% worked out yet, but you will be told before the switch occurs, and most employees are saying it will basically be billed as an Unbound Worker.
Hello, I’m Allie!
Pricing · Cloudflare Workers docs
Documentation for Cloudflare Workers, a serverless execution environment that allows you to create entirely new applications or augment existing ones without configuring or maintaining infrastructure.
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
Hello, I’m Allie!
Do you have the main field in your wrangler.toml set to the entry-point of your Worker?
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
Hello, I’m Allie!
Are you building the Worker yourself, or letting it bundle it for you?
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
Where is itty-router defined in your dependencies? In the root package.json, or in workers-site/package.json? Wrangler 1 handled things a little differently with Sites, but it's generally easier with wrangler 2 to just place all of these as devDependencies in your root package.json
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
Okay yeah, that file isn't being read or installed from. I would recommend pulling those dependencies into your root package.json, and nuking the package/package-lock from the workers-site folder with Wrangler 2
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
Kinda. You can make it work with the nested package.json, but it's just generally way easier not to bother these days with how well wrangler 2 handles bundling dependencies
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
It can be - it doesn't really matter. That field only really prevents you from running npm publish publicly
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
Complete rewrite in TypeScript instead of Rust
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
yeah, pretty much, from my understanding. With Workers being a JS ecosystem, it just made sense.
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
Do you have a minimal reproducible example? I don't have any familiarity with the github npm registry, but that package definitely does exist with traditional npm: https://www.npmjs.com/package/@cloudflare/kv-asset-handler
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
Seems like it might be some weird permission scoping with Github's registry if the package is private or something? https://github.com/orgs/community/discussions/25211
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
James
James2y ago
yeah I'm not super familiar with github's registry, but definitely seems like it's some config thing there
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
Hello, I’m Allie!
You can also try setting the registry to https://roxi.cloudflare.community. Probably won't fix anything, but doesn't hurt to try.
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View