-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements to @svelte-parts/drop-file #11
Comments
Hello @stophecom Long time no see. This repo does indeed need to be updated to work with later svelte versions. I need to check how svelte 3 components are supposed to be published. Do you know of an example with not too complex setup? |
Apparently you can prepare publishing packages with svelte-kit. import { DropFile } from 'svelte-parts' Looks like it works. Let me know if it does for you and I will move the other components to that library. I also added a |
I moved the whole thing to svelte-kit. for drop file you can use import DropFile from 'svelte-parts/DropFile.svelte' I kept the |
Oh cool. Sorry, didn't get notifications for that repo. I will add small PR for better types, maybe a |
On a side note. There are two more properties/attributes that eventually could be supported. (Although export let capture: 'user' | 'environment' | null = null
export let accept: string = '' // image/*, .gif etc. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file |
But like you mentioned. With drop you can't rely on any validation for e.g. for |
Hi A***, great repo!
I just checked out drop-file - it's great. I noticed that newer svelte version complains about typescript.
Also, I was wondering if the property
multiple
should be optional, since it would be better aligned with the native file input. (Also I only need one file in my app :))Let me know, I can create PR.
The text was updated successfully, but these errors were encountered: