I'm using wrangler to publish a worker, but there seems to be a bug. In my code I export default li

I'm using wrangler to publish a worker, but there seems to be a bug.

In my code I export default like so

export default { email };

export default { email };

export default { email };

export default { email };

When using

wrangler publish

wrangler publish

wrangler publish

wrangler publish it compiles to:

var src_default = { email };
export {
  src_default as default
};

var src_default = { email };
export {
  src_default as default
};

var src_default = { email };
export {
  src_default as default
};

var src_default = { email };
export {
  src_default as default
};

And in the dashboard when I try to test it it tells me

Email Trigger not available to this workers

Email Trigger not available to this workers

Email Trigger not available to this workers

Email Trigger not available to this workers

Though when I change it manually to the former again:

export default { email };

export default { email };

export default { email };

export default { email };

It seems to work and goes to the next error about a constructor.

WebberOP•2/25/23, 4:56 PM

Any ideas of what I can try?

kian•2/25/23, 5:01 PM

Sounds like their detection for an Email handler is a bit flaky - I’d post in #email-routing

Kkian Sounds like their detection for an Email handler is a bit flaky - I’d post in #e...

WebberOP•2/25/23, 5:13 PM

Thanks. I was thinking that, glad it looks that way to someone else as well

WebberOP•2/25/23, 5:15 PM

Is there any way to influence the compilation config in

wrangler.toml

wrangler.toml

kian•2/25/23, 5:17 PM

It works for other handlers so it does just seem to be their detection

kian•2/25/23, 5:17 PM

I'd say you can use --no-bundle--no-bundle to avoid bundling but that means you wouldn't be able to use any dependencies (like postal-mime)

kian•2/25/23, 5:19 PM

kian•2/25/23, 5:20 PM

You could try something like this? I don't see how it's any different personally but that's what I've seen other people use for Email Workers w/ Wrangler

kian•2/25/23, 5:20 PM

i.e https://github.com/Le0Developer/cloudflare-discord-mailing/blob/master/src/index.ts

Kkian i.e <https://github.com/Le0Developer/cloudflare-discord-mailing/blob/master/src/...

WebberOP•2/25/23, 5:51 PM

Yea my settings are identical to that repo. It's quite odd

WebberOP•2/25/23, 5:54 PM

Tried your suggestion to

export default {
  async email(message: EmailMessage, env: Env, ctx: ExecutionContext): Promise<void> {
    return await email(message, env, ctx);
  },
};

export default {
  async email(message: EmailMessage, env: Env, ctx: ExecutionContext): Promise<void> {
    return await email(message, env, ctx);
  },
};

Which compiles to

var src_default = {
  async email(message, env, ctx) {
    return await email(message, env, ctx);
  }
};
export {
  src_default as default,
  email
};

var src_default = {
  async email(message, env, ctx) {
    return await email(message, env, ctx);
  }
};
export {
  src_default as default,
  email
};

WebberOP•2/25/23, 5:55 PM

No joy

kian•2/25/23, 5:55 PM

Which version of Wrangler is this with?

WebberOP•2/25/23, 5:56 PM

I tried 2.11.0, 2.11.0 and 2.7.1

WebberOP•2/25/23, 5:56 PM

They have the exact same behaviour

WebberOP•2/25/23, 6:01 PM

Oh you were right Kian. It doesn't work when using an anonymous functionanonymous function stored into a
const
const
in combination with a non-
default
default
export. But when changing it to named function async function emailasync function email it stopped displaying the error that I had before. We're on to something

Edit: nope, spoke too soon. Not sure why that time the error didn't show up, but the behaviour is exactly the same

WebberOP•2/25/23, 6:09 PM

Even if I only compile the console.log like so, I'm still getting the error:

zegevlier•2/26/23, 12:24 PM

What you're looking for is HTML escaping. You should look that up for whatever language you're using. If you want to do it manually, you can replace the << with << and the >> with >>.

RRaindrops Im currently trying to render HTML with a worker

rdutton•2/26/23, 12:35 PM

This might help : https://codepen.io/rdutton/pen/PodbqEE

RRaindrops thank you so much!!

rdutton•2/27/23, 7:37 AM

No probs!

zegevlier•2/27/23, 1:18 PM

zegevlier•2/27/23, 1:19 PM

They're already in workerd, the open source runtime

Erisa•2/27/23, 1:20 PM

lets talk normally without the flies :D

TTippie What is workerd?

Erisa•2/27/23, 1:20 PM

https://github.com/cloudflare/workerd

GitHub

GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that pow...

The JavaScript / Wasm runtime that powers Cloudflare Workers - GitHub - cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers

kian•2/27/23, 3:49 PM

I've used aws-sdk-js-v3 in Workers but yeah, there's probably codepaths that rely on Node/Browser built-ins & it's a much larger bundle than aws4fetch

KKuttyz Is AWS SDK supported on Cloudflare page functions?

rdutton•2/27/23, 3:49 PM

It won't work as it is, due to relying on Node functions that won't be available in a Cloudflare worker context. Found this option online, might be worth a look - https://github.com/mhart/aws4fetch

Kkian I've used aws-sdk-js-v3 in Workers but yeah, there's probably codepaths that rel...

rdutton•2/27/23, 3:51 PM

Does it (e.g. wrangler) bundle the whole thing by default, or just the bits you use?

kian•2/27/23, 3:52 PM

esbuild will try to eliminate dead code - https://esbuild.github.io/api/#tree-shaking

kian•2/27/23, 3:52 PM

It's still orders of magnitude larger than aws4fetch

Kkian esbuild will try to eliminate dead code - <https://esbuild.github.io/api/#tree-s...

rdutton•2/27/23, 3:52 PM

Thanks, good to know

Hello, I’m Allie!•2/28/23, 9:32 AM

What's the best way to have

console.log

console.log

s in JS code that are automatically stripped out by

esbuild

esbuild

, unless some specific action is performed during the build?

HHello, I’m Allie!What's the best way to have `console.log`s in JS code that are automatically str...

Hello, I’m Allie!•2/28/23, 10:10 AM

Wrote a plugin for it:

const devRetainer = {
  name: "devRetainer",
  setup(build) {
    build.onLoad({ filter: /\.ts$/ }, async (args) => ({
      contents: (await readFile(args.path, "utf8")).replace(/(\/\* Debugging Statement Start)|(Debugging Statement End \*\/)/g, ""),
      loader: "ts",
    }));
  },
};

const devRetainer = {
  name: "devRetainer",
  setup(build) {
    build.onLoad({ filter: /\.ts$/ }, async (args) => ({
      contents: (await readFile(args.path, "utf8")).replace(/(\/\* Debugging Statement Start)|(Debugging Statement End \*\/)/g, ""),
      loader: "ts",
    }));
  },
};

Cyb3r-Jak3•3/1/23, 1:39 AM

Zone -> Workers Routes -> Edit maybe?

Chaika•3/1/23, 2:59 AM

hmm can't find anything in the docs about it and Discord search is still broken blobnotlikethis

I wonder if it's not Zone -> DNS -> Edit, since they show as DNS Records / are "sort of" DNS Level

Chaika•3/1/23, 3:09 AM

Account id / zone ids are fine to be public

I'm using wrangler to publish a worker, but there seems to be a bug. In my code I export default li

Similar Threads