wrangler publish

[threepointone]

This is the parent issue tracking the implementation of wrangler publish.

Usage

In it's simplest form, you can write a worker, say at index.js, and run: wrangler publish index.js --name myscriptname, and -

• it'll 'bundle' your script into a single file, and publish it to myscriptname.<your subdomain>.workers.dev
• Much like wrangler dev, we aim to provide a default experience that's immediately useful, so you shouldn't have to setup a bundler/compiler for most usecases. So, you can use modules from npm, create separate modules, use react (todo: --jsx <reference> for other libraries), use typescript, and it should all Just Work. (more details on the tracking issue for wrangler dev)
• Much like wrangler dev, wrangler publish will also automatically infer whether your script is in the service-worker format or the newer ES modules format.
• You can publish to your own domain/zone with wrangler publish <script> --name <name> --zone somedomain.com --route "somedomain.com/path/*"
  • You'll note that you can pass a domain directly to zone, instead of a zone_id. wrangler publish should work with both forms of configuration.

[huv1k]

Is there any plan to add a build step back to the public? Right now you need to compile your script before running publish what is kind of inconvenient.

[threepointone]

To clarify:

• Because we're using esbuild internally, most common usecases should just work without a compile step. So, if you're using npm modules, jsx, typescript etc, you shouldn't have to do a build step at all. Just point to your entry point and it should just work. (we're also reading the entrypoint from build.upload.main like wrangler1, but this hasn't been tested throughly).
• If you do need need to run a build before dev/publish, we're thinking of doing what pages dev does, which is being able to pass the build step directly to dev/publish after --. So for example, if your build step is webpack, you should be able to do wrangler publish output/index.js -- webpack (assuming webpack outputs the worker to output/index.js) This isn't implemented yet, but should be done before the end of next week.
• With this in place, we're probably going to deprecate having build.command in wrangler.toml, unless there's pushback.

Does this make sense, and is acceptable to you?

[threepointone]

A remaning task here is to implement custom builds. Tracking that here #120 and closing this issue.