This uploading wrapper remains fully functional and can be a great fit for your projects, especially if you have specific needs for jQuery. However, we recommend exploring our new web component-based File Uploader to access the latest features and improvements.
Angular 2+ wrapper for Uploadcare jQuery File Uploader.
jQuery File Uploader is a part of the Uploadcare ecosystem.
For Angular v14+ — install ngx-uploadcare-widget v4.x
npm install ngx-uploadcare-widget@4.x uploadcare-widget
For Angular v12+ — install ngx-uploadcare-widget v3.x
npm install ngx-uploadcare-widget@3.x uploadcare-widget
For Angular from v9 to v11 — install ngx-uploadcare-widget v2.x
npm install ngx-uploadcare-widget@2.x uploadcare-widget
For Angular v8 and lower — install ngx-uploadcare-widget v1.x
npm install ngx-uploadcare-widget@1.x uploadcare-widget
The basic wrapper usage scenario can be described in four steps.
import { UcWidgetModule } from 'ngx-uploadcare-widget';
@NgModule({
imports: [
...,
UcWidgetModule,
],
...
})
...
<!-- with default markup -->
<ngx-uploadcare-widget
public-key="YOUR_PUBLIC_KEY"
[images-only]="true">
</ngx-uploadcare-widget>
<!-- without any markup -->
<ngx-uploadcare-widget-custom
public-key="YOUR_PUBLIC_KEY"
[images-only]="true">
</ngx-uploadcare-widget-custom>
The component currently supports three widget events:
on-change
on-upload-complete
on-progress
Here is how you can handle those three,
<ngx-uploadcare-widget
public-key="demopublickey"
[images-only]="true"
(on-upload-complete)="yourOnUploadHandler($event)"
(on-change)="yourOnChangeHandler($event)"
(on-progress)="yourOnProgressHandler($event)">
</ngx-uploadcare-widget>
You can learn more about this widget events in our docs.
All the following attributes correspond to the ones listed in the
widget docs, but without the data-
prefix.
- public-key
- multiple
- multiple-max
- multiple-min
- images-only
- preview-step
- crop
- image-shrink
- clearable
- tabs
- input-accept-types
- preferred-types
- system-dialog
- secure-signature
- secure-expire
- value
- cdn-base
- do-not-store
- validators
- on-upload-complete
- on-change
- on-progress - fired several times while upload with progress data.
Events usage example:
onUpload(info) {
console.log('fired Event "onUpload"');
console.log(info);
}
onProgress(progress) {
console.log('fired Event "onProgress with data:"');
console.log(progress);
}
onChange(file) {
if(!file) {
return;
}
console.log('fired Event "onChange"');
// input file parameter depends on "multiple-files" widget attribute
if(this.multipleFiles) {
// file contains 2 methods:
// .promise() - returns the general promise for all uploaded files which resolves into an uploaded file group info
// .files() - returns an array of promises: one per each uploaded file. Each promise resolves into an uploaded file info
console.log(file);
if(file.promise) {
file.promise().then((groupInfo) => {
console.log('resolved general promise from "onChange" with data:');
console.log(groupInfo);
});
}
if(file.files) {
file.files().forEach((promise) => {
promise.then((fileInfo) => {
console.log('resolves file promise with file info:');
console.log(fileInfo);
});
});
} else {
// file contains uploaded file info
console.log(file);
}
}
}
The components provides following public methods:
-
clearUploads()
- Removes all current uploads from the widget. You can use the method to reset a form even if a user has already uploaded some files. -
reset(clearUploads = false)
- Resets the widget, You can also remove all the current uploads ifclearUploads
is set totrue
-
openDialog()
- Opens the widget dialog with current configuration. -
reject()
- Closes the dialog opened withopenDialog()
method only and discards any file selection.
All methods are accessible from a parent component via the @ViewChild()
approach.
It is possible that your locale is not available in the widget yet. If that’s the case, contributing your locale might be a good idea. This can be done by forking the main repository and adding a localization file here.
The quick way of implementing your locale would be overriding any of the
existing ones via the UPLOADCARE_LOCALE_TRANSLATIONS
property.
If you think you ran into something in Uploadcare libraries which might have security implications, please hit us up at bugbounty@uploadcare.com or Hackerone.
We'll contact you personally in a short time to fix an issue through co-op and prior to any public disclosure.
Issues and PRs are welcome. You can provide your feedback or drop us a support request at hello@uploadcare.com.