-
Notifications
You must be signed in to change notification settings - Fork 337
allow for wrangler publish
without npm install
#778
Comments
I think that this is sort of related to #428 (comment) |
Yeah, I hear that — related to this would be supporting FWIW I worked around this by committing an empty package.json adjacent to the worker.js file, resulting in a no-op |
The more I've thought about this the less I think Decoupling those steps and allowing the "target" directory to be configurable (like |
@gusvargas In my opinion, that's the ideal case. However, you are missing context and implementation details here. We did focus on UX by installing the user's dependecies (if needed). |
Closing in favor of #820, please track work there. |
I have the same issue where I don't believe wrangler should really have anything to do with builds, but I get it's there to give a good out the box experience. I did in the end write a example custom script I'll share for anyone interested that uploads the built worker and a KV asset via the API, bypassing wrangler. https://github.com/samkelleher/wasm-embed/blob/master/src/deploy.mjs If your use case is just for publishing, this might be of use. |
💡 Feature request
Overview and problem statement
Livepeer has a Yarn monorepo and running
npm install
in it kind of mucks things up. I've already got a completely compiledworker.js
suitable for uploading as a Cloudflare worker, as well as a static HTML Next.js site that I'd like uploaded to Workers Sites. I don't need any of thenpm
automation provided bywranglerjs
, but it'd still be nice to be able to usewrangler publish
.Here's the wrangler.toml I'm using.
Basic example
Seems like it'd be a configuration flag in
wrangler.toml
?The text was updated successfully, but these errors were encountered: