🚀 Feature Request: [Wrangler 2 Regression] Being able to inspect the worker code

Describe the solution

Wrangler 1 was generating the worker code locally on my machine, and added the worker code to my source tree, so I could easily inspect it.

Wrangler 2 most likely also generates the worker code locally on my machine, but I can’t find where it then lives? Is it written to the filesystem somewhere? Being able to inspect the worker code is paramount for debugging.

I know I can inspect the worker code on couldflare.com’s UI but that’s quite inconvenient.

(Btw. wrangler 2 is much better than wrangler 1, nice job 👌.)

[brillout]

With beta it’s still off:

Error thrown while running $ wrangler dev:

Error: [telefunc@0.1.22][Wrong Usage] Using `telefunc()` (`import { telefunc } from 'telefunc'`) is forbidden on the client-side, see https://telefunc.com/isomorphic-import
    at worker.js:491:7
    at handleTelefunc (worker.js:497:32)
    at handleFetchEvent (worker.js:560:31)
7:47:02 AM POST /_telefunc 500

The worker code generated by $ wrangler publish --dry-run:

  494   async function handleFetchEvent(event) {                                                                                                                    
  495     const { url } = event.request;                                                                                                                            
  496     const { pathname } = new URL(url);                                                                                                                        
  497     if (pathname.startsWith("/_telefunc")) {                                                                                                                  
  498       const body = await event.request.text();                                                                                                                
  499       const { method } = event.request;                                                                                                                       
  500       const response2 = await handleTelefunc({ url, method, body });                                                                                          
  501       return response2;                                                                                                                                       
  502     }                                                                                                                                                         
  503     const response = await handleStaticAssets(event);                                                                                                         
  504     return response;                                                                                                                                          
  505   }    

Note how handleTelefunc() lives at line 500 which doesn’t match the stack trace.

using a custom build, you can skip wrangler’s bundling altogether with --no-bundle

Neat & I can confirm that works:

wrangler publish --dry-run --outdir worker-build 

wrangler dev --no-bundle worker-build/index.js 

I can start debugging now. And, yes, I think it’d be great to document this. This makes debugging 10x more fun.

(FYI I’m debugging Telefunc’s Cloudflare support.)

Thanks! I guess we can close this then.

[threepointone]

Could you try with the @beta version? We landed a fix for error stacks that we’ll release next week. Alternately, if you’re using a custom build, you can skip wrangler’s bundling altogether with --no-bundle (in both dev and publish)