This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.
# Releases
## @uppy/locales@4.8.4
### Patch Changes
- ea04a4d: Add "files" in package.json to only publish what's needed
## @uppy/transloadit@4.3.3
### Patch Changes
- ee0b2fc: Add `user_meta` type to `AssemblyResult`
## uppy@4.18.2
### Patch Changes
- ea04a4d: Add "files" in package.json to only publish what's needed
- Updated dependencies [ee0b2fc]
- Updated dependencies [ea04a4d]
- @uppy/transloadit@4.3.3
- @uppy/locales@4.8.4
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
**Problem**
- `@uppy/locales` on npm used to have `dist` (minified), `lib` (JS),
`src` (to make the sourcemaps work) but dist is redundant tbh and only
for the CDN
- Since the new release tooling only `lib` was published to npm
- CI release could not find any files to upload to CDN (it uses
npm-pack, which checks the "files" in package.json and `dist` was
missing)
**Solution**:
- Correct "files" in package.json's
- Remove `main` from @uppy/locales package.json which pointed to
something random?
We still publish `dist` for `@uppy/locales` needlessly to npm afaik.
Would require a bit more hacking to separate in the current setup
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.
# Releases
## @uppy/dashboard@4.4.3
### Patch Changes
- c15c6fd: Make each entry in `strings` in locale type optional
- Updated dependencies [c15c6fd]
- @uppy/status-bar@4.2.3
## @uppy/locales@4.8.3
### Patch Changes
- 1a0beb9: Add all locales to globalThis.Uppy.locales.[locale-name]
## @uppy/status-bar@4.2.3
### Patch Changes
- c15c6fd: Make each entry in `strings` in locale type optional
## uppy@4.18.1
### Patch Changes
- Updated dependencies [c15c6fd]
- Updated dependencies [1a0beb9]
- @uppy/status-bar@4.2.3
- @uppy/dashboard@4.4.3
- @uppy/locales@4.8.3
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.
# Releases
## @uppy/svelte@4.6.2
### Patch Changes
- 4aa708a: Fix prop passing and types
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.
# Releases
## @uppy/angular@0.9.2
### Patch Changes
- 8f8ee09: Nothing changed, just a release to fix the broken previous
release.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.
# Releases
## @uppy/angular@0.9.1
### Patch Changes
- 7eec173: Remove "files" array from package.json
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Closes#5759Closes#5833.
This PR:
- Introduces updates in @uppy/angular that improve developer experience
(DX) and also address open issues
The @uppy/angular package underwent major updates in v0.80
([27492bc](27492bca8a)),
where we dropped support for NgModules in favor of standalone
components. This change aligns with the direction set by the Angular
team — starting from Angular v17, and becoming default in v19, all
components are standalone by default. This is now the recommended way to
build UI components in Angular.
However, the docs and examples have not yet been updated to reflect
this. That will be addressed in #5818.
Even though components are standalone by default starting from Angular
17+, it is still considered good practice to explicitly declare them as
standalone. This is also validated by the Angular LSP, which raises an
error when this declaration is missing.
<img width="1042" height="742" alt="image"
src="https://github.com/user-attachments/assets/1f557871-c302-4f02-9ded-ddf27c6175bd"
/>
Changes in this PR:
- Explicitly mark all components as standalone
- Fix demo components
- Add support for Angular 20
---------
Co-authored-by: Merlijn Vos <merlijn@soverin.net>
Closes#5865
I noticed we are publishing all files, we should filter them. npm
automatically adds package.json, license, and readme so you can leave
them out of the files array.
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.
# Releases
## @uppy/redux-dev-tools@4.1.2
### Patch Changes
- 1d43639: Nothing, testing release tooling
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.
# Releases
## @uppy/redux-dev-tools@4.1.2
### Patch Changes
- c71a8e7: Nothing, testing release tooling
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.
# Releases
## @uppy/locales@4.8.0
### Minor Changes
- 28f0886: Move dev dependencies from "dependencies" to
"devDependencies"
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
- Deduplicate Vite versions, always use 7.x (except for sveltekit, which
does not allow 7 yet)
- Add missing dev deps
- Fix react-native requested deps versions
- Fix companion @types/node
- Fix "engines" in root package.json
No more yarn warnings 🎉
This adds the option to pass a getter to the `endpoint` option of the
`@uppy/xhr-upload` plugin:
```ts
.use(XHRUpload, {
endpoint: (file) => createSignedUrl(file),
})
```
This is especially useful when the backend uses short-lived signed urls
for uploads.
---------
Co-authored-by: Merlijn Vos <merlijn@soverin.net>
- Remove `e2e` folder entirely
- Remove all hacky resolutions and yarn patches
- Remove `@types/jasmine`, `js2ts` (convert a JS file to TS), and
`vue-template-compiler` from `private/`
- Remove e2e CI job
- Add browsers tests for vue, svelte, and react headless components and
hooks.
- Add new (browser) tests for transloadit, aws-s3, and dashboard.
- Remove final useless scripts from `package.json`, use direct
references in CI.
- Fix Dropzone component accessibility discovered during testing
- Clean up github workflows (move linters.yml into ci.yml, update
e2e.yml)
**Why Vitest Browser Mode?**
We could have used playwright but vitest browser mode uses it under the
hood and we get the use the vitest we know a love. No two entirely
different setups, no different assertions to relearn, write e2e tests as
if you're writing unit tests. Easy, fast, beautiful.
https://vitest.dev/guide/browser/
**Has every single e2e test been rewritten?**
No there were quite a few tests that have a lot overlap with existing or
newly added tests. There were also some tests that were so heavily
mocked inside and out you start to wonder what the value still is. Open
to discuss which tests still need to be added.
Closes#5822
- `"^build"` makes sure dependencies of the package are build first.
- Make dependencies of @uppy/components actually dependencies
- Remove concurrency setting. It was too high for computers with low
RAM.
Closes#5774
There are still some warnings left but they are better done in their own
PRs as they require bigger changes.
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
As of Node.js 24+ `FormData.append()` will crash when we pass our
`StreamableBlob` because it became more strict. This PR makes it spec
compliant.
---------
Co-authored-by: Mikael Finstad <finstaden@gmail.com>
- Upgrade vitest from 1.x to 3.x.
- Fix some tests that now became more strict and started failing
- Add test command to all packages + needed dependencies
- Add turbo config for running tests
Another PR will completely redo the e2e test suite.
- Add `typecheck` command to all packages.
- Use turbo to build and watch concurrently with caches.
- Remove root `bin/` folder with last global scripts
- `bin/companion.sh` -> `@uppy/companion/start-dev` (`yarn
start:companion` still works)
- `bin/build-components.mjs` -> `@uppy/components/migrate.mjs` (`yarn
migrate:components` can be used to run it). This only needs to be ran
for new components, not changing existing ones, so that's why it's not
part of the build process.
turbo is smart enough to build dependencies within a package first
before building the package itself (e.g if wanting to build @uppy/audio,
build @uppy/utils first). Unfortunately @uppy/core is a peer dep
everywhere turbo does not take it into account, yet it must be build
first to avoid race conditions. Therefor I added a turbo.json to each
package, which you normally never need, but this is an odd case I
suppose. Other solutions ran into cyclic dep errors.
Another PR would move over the test commands to turbo too.
- Isolate CSS bundling per package
- Fix _all_ sass deprecation warnings
- Remove global scripts
- Run CSS building in parallel .
Is it repetitive? Yes a bit. But it's mono repo best practice and once
we introduce turbo each css build step can be individually cached. That
means when you edit scss in one package, only that needs to be rebuild,
not the TS of that package nor any other CSS. This PR lays the
groundwork for that.
