Uncaught ReferenceError: Buffer is not defined

Hi! I’m having this weird error message using Vite as a bundler which seems to happen in a very specific scenario.

I couldn’t reproduce it using the default vite dev server (ie.: npx vite), but I managed to create a small repro of the scenario I have in another project that uses Phoenix and does not use vite’s dev server.

I can confirm though that the error only happens when the last import is present (@uppy/transloadit):

import Uppy from '@uppy/core'
import Dashboard from '@uppy/dashboard'
import Transloadit from '@uppy/transloadit'

---

Creating an simple HTML file and adding a script tag to the head works fine using vite’s dev server (npx vite):

index.html

<script type="module">
  import Uppy from '@uppy/core'
  import Dashboard from '@uppy/dashboard'
  import Transloadit from '@uppy/transloadit'
<script>

But it doesn’t work if I use vite build with my current config for some reason. Here’s a small repro that illustrates the problem: vite-repro.zip

Instructions:

• npm i --prefix assets
• npm run build --prefix assets
• npm run start --prefix assets (for the HTTP server).
• See error in Chrome dev tools (I’m using version 94.0.4606.81)

[Murderlon]

It was a bit of a confusing process to reproduce this with only socket.io-client and not through @uppy/transloadit but I did in the end. I reported it to them (see reference above) and offered interest in contributing, but it seems I can’t fix this on our side as it seems to be a dual publishing issue on their end.

[RobWalker]

@thiagomajesk my current work around is to load uppy from the CDN rather than bundle it via vite, basically add:

<script src="https://releases.transloadit.com/uppy/v2.2.3/uppy.min.js"></script>

to index.html and then use window.Uppy to reference it from the code … it is far from ideal, but it does work and our project still has a ways to go before hitting production and we can punt on this for a little longer in the hope of a more formal fix.