#`deno bundle` and React Router

6 messages · Page 1 of 1 (latest)

shadow sinew
#

Is bundle intended to fully cover projects would normally require third party build tools? Asking primarily because I ran into a snag trying to migrate a React project off of Vite -- that snag appearsto involve React Router -- which, itself, uses Vite as a dev dependency.

(Tangentially, if I keep using Vite, its syntax parsing throws errors on attempting to use text imports)

low drift
#

The deno bundle command in its current form is not a replacement for something like vite. It only does bundling like merging js files together. There is no dev server, no HMR and no plugin support.

shadow sinew
#

Got it. Is that just an immediate-term statement about its experimental status, or also a medium- to long-term one about its design?

low drift
#

time will tell, but stay with vite for the foreseeable future.

ashen timber
#

Friendly note @low drift, (from someone who loves the old and new deno bundle)

The deno bundle command in its current form is not a replacement for something like vite.

Could be definitely be more clearly communicated on the site docs and in the 2.4 announcement.

Ex [current docs]:

This tool is useful for deploying or distributing a project as a single optimized JS file

Could continue with:

, but is not currently intended as a replacement for complex or interactive build tools such as Vite or Webpack.

Just half a sentence could go a long way for setting up correct expectations..

low drift