* @uppy/companion: remove `lodash` dependency
* @uppy/companion: test the transpiled files instead of source
* @uppy/companion: rollback to using `lodash.merge`
* Revert "@uppy/companion: test the transpiled files instead of source"
This reverts commit 5ffd5786f1.
* @uppy/companion: remove Node.js v10 and v12 from the CI, add v16
* @uppy/companion: remove Node.js v16.x from the CI
* Revert "@uppy/companion: remove Node.js v10 and v12 from the CI, add v16"
This reverts commit 9dca738f2a.
* Remove optional chaining to keep Node.js v12 support
* master: (23 commits)
A bit of polish (#2986)
Companion: Fix typescript error
Companion: Fix invalid referrer crashing the process
Publish 1.30 blog post
Release
Build: Companion needs to be built before locale-pack
Release
Fix build: locale-pack first, integrations second
changelog for 1.30
Release
Update package.json
Only log info if debug is true (#2855)
build(deps): bump prismjs from 1.23.0 to 1.24.0 (#2971)
Angular Integration (#2871)
ci: don't run markdown tests in type tests
Add types for `uppy.once` method (#2965)
build: lint fixes in build scripts
Fix typo in docs/progressbar.md (#2962)
Document `uppy.once` in `docs/uppy.md` (#2960)
Add `props` example to docs/vue.md (#2959)
...
* Remove IE polyfills and special casing
* dashboard: remove `resize-observer-polyfill`
* deps: remove url-parse to use global `URL` instead
* Update documentation for browser support
* Add a migration guide
* Update e2e test platforms
* Remove polyfills from examples and add those missing in CDN bundle
* Use Node.js v16.x on CI because of `AbortController`
* Update bundle builder to produce two builds: `uppy.js` without polyfills, `uppy.legacy.js` with polyfills.
* Upgrade create-react-app deps
* remove null coalescing operator as it's not supported by the build chain
* disable Safari testing (for now)
Co-authored-by: Renée Kooi <renee@kooi.me>
Unfortunately I can't figure out how to make the dependencies and
versions work out well here.
Instead, this uses a custom slide transition component. It is much more
simple than preact-css-transition-group, which supports animating groups
of components. The `<Slide />` component:
- can only support one element, that either exists or does not exist
- requires that the child element takes a `className` property, that it
passes onto its root element
- only uses `setTimeout()` for when the transition finishes
(in preact-css-transition-group, the `transitionend` event is used,
which is more _accurate_ but less _reliable_)
- hardcodes the transition duration
- hardcodes the transition name
This makes it much more limited. Hopefully the reduced complexity is
worth it.
If we have other transitions in the future, we can copy-paste this
component.
