I just tried to make svelte-dropzone run as a sapper/svelte app with the standard template, just replacing index.svelte with your code - with no success. You readme looks great and easy, but then it doesn't work, as other issues are stating.
Your npm package is downloaded 50 times a week, which means that about 200 people spend 10 minutes or even hours with your software every month, trying to make it work.
It would be great if you could
1) Update the instructions so it runs with the basic sapper template
2) Fix the code if this is required to make it work
3) Fix the npm package as some issues state it has errors
4) Or - at least - write in bold letters, that this is not maintained. I think that's just fair.
Here is my little test:
$ npx degit "sveltejs/sapper-template#rollup" droptest
$ cd droptest
$ npm i
$ npm i svelte-dropzone
### replace index.svelte content with code from readme
$ npm run dev
> TODO@0.0.1 dev /droptest
> sapper dev
✔ server (2.3s)
✔ client (2.9s)
✔ service worker (27ms)
/droptest/node_modules/svelte-dropzone/index.svelte:1
<script>
^
SyntaxError: Unexpected token '<'
at wrapSafe (internal/modules/cjs/loader.js:1072:16)
at Module._compile (internal/modules/cjs/loader.js:1122:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
at Module.load (internal/modules/cjs/loader.js:1002:32)
at Function.Module._load (internal/modules/cjs/loader.js:901:14)
at Module.require (internal/modules/cjs/loader.js:1044:19)
at require (internal/modules/cjs/helpers.js:77:18)
at Object.<anonymous> (/droptest/__sapper__/dev/server/server.js:10:32)
at Module._compile (internal/modules/cjs/loader.js:1158:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
> Server crashed
Anyway, thanks for sharing your code - I was looking for a solution like this.
Hi Arnoud,
I just tried to make svelte-dropzone run as a sapper/svelte app with the standard template, just replacing
index.sveltewith your code - with no success. You readme looks great and easy, but then it doesn't work, as other issues are stating.Your npm package is downloaded 50 times a week, which means that about 200 people spend 10 minutes or even hours with your software every month, trying to make it work.
It would be great if you could 1) Update the instructions so it runs with the basic sapper template 2) Fix the code if this is required to make it work 3) Fix the npm package as some issues state it has errors 4) Or - at least - write in bold letters, that this is not maintained. I think that's just fair.
Here is my little test:
Anyway, thanks for sharing your code - I was looking for a solution like this.