bc7f703916
* transloadit: Add barebones base plugin. * tus: Add `uninstall` method. * transloadit: Implement creating assemblies and hacky tus-uploading. * transloadit: Add test file (Just checking options errors for now) * transloadit: Link to templates overview page in `templateId` error. * transloadit: Use dynamic tus endpoint from assembly result. * core: Implement uploader pre- and postprocessors and async flow. * tus: Merge in tus options from `file` objects. This will allow preprocessor plugins to configure tus uploads. * transloadit: Implement as a `preprocessor` handler. * transloadit: Add status socket connection.Add `wait` option to wait for assembly to finish before resolving. * dashboard: Log errors to console if the upload fails at any point. * transloadit: Add `waitForEncoding`, `waitForMetadata` options instead of just `wait`. * transloadit: Merge in params from `params` option when creating an assembly. * transloadit: Docc why we set the `file.meta` property. * transloadit: Support the API key being passed in via `params.auth.key`. This way developers can dump a JSON payload for transloadit into the `params` option. That'd be especially useful for `signature`s. * transloadit: Only add `template_id` param to assembly if a `templateId` option is given. * transloadit: Add a `signature` pass-thru option. * transloadit: Remove `key` and `templateId` options--use `params` instead. * Transloadit: Throw a useful error when `params` is an invalid JSON string. * Transloadit: Check for existence of `params` before validity. * Transloadit: Fix adding post-processor. * Transloadit: No need to get assembly status after creating one. * Transloadit: Add logs in a few places * Transloadit: Get assembly status after upload is complete. It's unused for now, but we should use eg. the results status to provide feedback, especially if the assembly failed. Maybe the `uploads` key in the result will also contain useful data if the uploads fail? * Transloadit: Add a pass-thru `fields` option… This one should be runtime-configurable in some other way too. Maybe by passing a <form /> element, or with the MetaData plugin… * Transloadit: Always connect to the assembly status socket. * Transloadit: Emit a `transloadit:result` event for assembly results. But only when `waitForEncoding` is true! * transloadit: Some doc comments for the main classes |
||
|---|---|---|
| bin | ||
| example | ||
| src | ||
| test | ||
| website | ||
| .babelrc | ||
| .browsersync.js | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .travis.yml | ||
| ARCHITECTURE.md | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| env.example.sh | ||
| LICENSE | ||
| Makefile | ||
| package.json | ||
| README.md | ||
| SERVER-PLAN.md | ||
| UPPY-CALL.md | ||
| uppy-screenshot.jpg | ||
Uppy
Uppy is (going to be) a sleek, modular file uploader that integrates seemlessly with any framework. It fetches files from local disk, Google Drive, Dropbox, Instagram, remote URLs, cameras and other exciting locations, and then uploads them to the final destination. It’s fast, easy to use and let's you worry about more important problems than building a file uploader.
Uppy is developed by the Transloadit team.
Check out uppy.io for docs, API, examples and stats.
Features (some in development)
- Lightweight, modular plugin-based architecture, easy on dependencies ⚡
- Use from a CDN or as a module to import
- Resumable file uploads via the open tus standard
- Supports picking files from sources like: Webcam, Dropbox, Facebook, bypassing the user's device where possible, syncing between servers directly via uppy-server
- A nice user interface ✨
- Speaks multiple languages (i18n) 🌍
- Built with accessibility in mind
- Free for the world, forever (as in beer 🍺, pizza 🍕, and liberty 🗽)
- Works great with file encoding and processing backends, such as Transloadit, works great without (just roll your own Apache/Nginx/Node/etc backend)
- Cute as a puppy, also accepts cat pictures 🐶
Demo
Usage
⚠️ 🚧 Don’t use Uppy in production just yet, we’re working on it
Installing from NPM
$ npm install uppy --save
Bundle with Browserify or Webpack:
import Uppy from 'uppy/lib/core'
import DragDrop from 'uppy/lib/plugins/DragDrop'
import Tus10 from 'uppy/lib/plugins/Tus10'
const uppy = Uppy()
uppy
.use(DragDrop, {target: 'body'})
.use(Tus10, {endpoint: '//master.tus.io/files/'})
.run()
Add CSS uppy.min.css, either to <head> of your HTML page or include in JS, if your bundler of choice supports it — transforms and plugins are available for Browserify and Webpack.
Give Uppy a spin on RequireBin.
Installing from CDN
But if you like, you can also use a pre-built bundle, for example from unpkg CDN. In that case Uppy will attach itself to the global window object.
1. Add a script to your the bottom of your HTML’s <body>:
<script src="https://unpkg.com/uppy/dist/uppy.min.js"></script>
2. Add CSS to your HTML’s <head>:
<link href="https://unpkg.com/uppy/dist/uppy.min.css" rel="stylesheet">
3. Initialize:
<script>
var uppy = new Uppy.Core({autoProceed: false, debug: true})
uppy.use(Uppy.DragDrop, {target: '.UppyDragDrop'})
uppy.use(Uppy.Tus10, {endpoint: '//master.tus.io/files/'})
uppy.run()
</script>
API
Uppy exposes events that you can subscribe to in your app:
Event core:upload-progress when file upload progress is available
uppy.on('core:upload-progress', (data) => {
console.log(data.id, data.bytesUploaded, data.bytesTotal)
})
Event core:upload-success when one upload is complete
uppy.on('core:upload-success', (fileId, response) => {
console.log(response.url)
var img = new Image()
img.width = 300
img.alt = fileId
img.src = response.url
document.body.appendChild(img)
})
Event core:success when all uploads are complete
uppy.on('core:success', (fileCount) => {
console.log(fileCount)
})
Browser Support
Note: we aim to support IE10+ and recent versions of Safari, Edge, Chrome, Firefox and Opera. IE6 on the chart above means we recommend setting Uppy to target a <form> element, so when Uppy has not yet loaded or is not supported, upload still works. Even on the refrigerator browser. Or, yes, IE6.
FAQ
React support?
Yep. Uppy-React component is in the works, in the meantime you can just use it as any other lib with React, see here.
Can I use it with Rails/Node/Go/PHP?
Yes, whatever you want on the backend will work with Multipart plugin, since it just does a POST request. If you want resumability, use one of tus implementations 👌🏼
Do I need to install special service/server for it?
No, as mentioned previously, Multipart plugin is old-school and just works with everything. However, you need uppy-server if you’d like your users to be able to pick files from Google Drive or Dropbox (more services coming). And you can add tus if you want resumability.
Does it support S3 direct upload?
Not at the moment, but you can write a plugin and send us a PR. That would be awesome :)
Contributions are welcome
- Contributor’s guide in
website/src/guide/contributing.md - Architecture in
website/src/api/architecture.md - Changelog to track our release progress (we aim to roll out a release every month):
CHANGELOG.md