gotjoshua

> What does your `permissions` object look like ```ts const suffix = '-test3' export const appNameObj = { name: `color-schemes${suffix}`, creator: `1zm${suffix}`, } const publicDirectoryArray = [ wn.path.directory(appNameObj.creator, appNameObj.name), wn.path.directory(appNameObj.creator,...

> Does this work when you request permissions for the entire public directory? I'll need to check later... neck deep in other stuff and no longer interested in using cat...

I'm looking into these two libs so far: https://github.com/jimmywarting/native-file-system-adapter/ https://github.com/GoogleChromeLabs/browser-fs-access anyone know of others worth considering?

I did some tests today. It seems that the file system access api is very impractical to use in worker contexts. Possible but rather impractical ([especially for writing new files](https://chromium.googlesource.com/chromium/src/+/lkgr/docs/security/permissions-for-powerful-web-platform-features.md#session_based-access-is-granted-by-direct-user-consent))....

still an issue with 0.32.0 and skypack seems to have problems with that auth module as well: 

[started a PR](https://github.com/fission-codes/fission-guide/pull/30). --- > can rename that section in GitBook to "Sharing Data" - [x] done

curious if there are any updates here? (both to the threat model discussion and the warming up issue)

> Testing now. @faddat any luck?

Well i found your far sexier endeavor over at unocss... and i pivoted hard. I guess uno is the main reason that this project seems a bit abandoned, right?

i have a fix for this: https://github.com/onezoomin/react-image-picker/commit/181acd417ec992560980667046661a5caccc91be will clean up and PR soonish