Nope. There is theoretically a binding that has it but it's not stabilised so it could be removed/br
Nope. There is theoretically a binding that has it but it's not stabilised so it could be removed/broken at any time.
"foo" then it will be an identifier rather than a string).name property - I think they'd be open to adding it onto that binding though, I don't see why not.name and deployment revision number & timestamp on the new one tooexport { Foo } from './foo' in your index.js/tsexport, not import.
otel-cf-workers package setup, so I'd want to attach logs to traces automatically and have the logs easily searchable within Baselime.
--definedefine"foo".namenamenumbertimestampexport { Foo } from './foo'exportimportotel-cf-workers{"name":"test-worker","deployment":{"id":"1a737aad-3c1a-40bf-90aa-4c0d1f840e13","number":51,"timestamp":"2024-04-27T02:52:40.970522Z"}}{"id":"72412edc-6438-4fe1-82b9-310ef69844f0","tag":""}// entrypoint/userEntrypoint.ts
// Not recognize in this file
export class UserStore extends WorkerEntrypoint<Env> {
...
}// index.ts
// If I copy all UserStore content in index, it's ok.
export default class extends WorkerEntrypoint {
async fetch() {
const response = `
Version: 1.0.0\n
Code Name: Piston
Description: Database Worker\n
Changes: Initial version\n
Health Check: OK
`;
return new Response(response, { status: 200 });
}
}import { UserStore } from "./entrypoints/userEntrypoint"[define]
WORKER_NAME = '"foo"'[[unsafe.bindings]]
name = "METADATA"
type = "metadata"