gitea/web_src/js/features/dropzone.js

export default async function createDropzone(el, opts) {
  const [{Dropzone}] = await Promise.all([
    import(/* webpackChunkName: "dropzone" */'dropzone'),
    import(/* webpackChunkName: "dropzone" */'dropzone/dist/dropzone.css'),
  ]);

  Dropzone.autoDiscover = false;
  return new Dropzone(el, opts);
}
Move dropzone.js to npm/webpack (#10645) - unvendor dropzone and upgrade it from 4.2.0 to 5.7.0 - make `csrf` available on window.config 2020-03-07 22:06:15 +01:00			`export default async function createDropzone(el, opts) {`
Fix Dropzone following #15315 (#15353) * Fix Dropzone following #15315 #15315 appears to have caused a change in the way Dropzone is imported - and it now produces a module rather than the constructor. This PR rather hackily just adds another Dropzone call to the result. Signed-off-by: Andrew Thornton <art27@cantab.net> * use destructured export Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: 6543 <6543@obermui.de> 2021-04-09 04:32:30 +02:00			`const [{Dropzone}] = await Promise.all([`
Move dropzone.js to npm/webpack (#10645) - unvendor dropzone and upgrade it from 4.2.0 to 5.7.0 - make `csrf` available on window.config 2020-03-07 22:06:15 +01:00			`import(/* webpackChunkName: "dropzone" */'dropzone'),`
			`import(/* webpackChunkName: "dropzone" */'dropzone/dist/dropzone.css'),`
			`]);`

			`Dropzone.autoDiscover = false;`
			`return new Dropzone(el, opts);`
			`}`