Contribution Date
Technology
Contribution Project
Contribution Details
Just going to share my own observations here:
- Using bower-asset/dropzone doesn't work as mentioned before.
- Using npm-asset/dropzone works, at least for now.
- There is a packagist specific repo that is maintained by the same team. However, the directory structure is slightly different.
While npm-asset works, I am encouraged to use the official repo (enyo/dropzone
). Yes, that won't be placed in the correct location for Drupal which means we need to write a custom entry in the repositories
section. One way out would be to support both by checking two paths: the current one which is dist/min/dropzone.min.js
and the one used in the new repo at dist/dropzone-min.js
. You can see all the files here: https://github.com/dropzone/dropzone-packagist/tree/master/dist
Issue Status
Active
Contribution Issue Link
Files count
0
Patches count
0