Alex Hoyau

cool :+1:

I believe it is because of the headers: `The resource at “https://github.com/warpdesign/react-explorer/raw/master/img/feature-darktheme.gif” was blocked due to its Cross-Origin-Resource-Policy header (or lack thereof). See https://developer.mozilla.org/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)#` 

I ended up writing this script as a workaround It runs a command in all project to link all the projects ```js #!/usr/bin/env node const metaLoop = require('meta-loop') const fs...

Hi @acrois I don't really remember but I guess I could check it out @mateodelnorte are you still around and accepting PRs?

Hi I am still on this one, for now using [this script](https://github.com/silexlabs/silex-meta/blob/main/scripts/link-all.js) as described [in the readme](https://github.com/silexlabs/silex-meta#about-this-meta-repo) Once it is working properly i'll do a PR

I tried to follow the instructions on this repo https://github.com/karol-f/meta-repository It produces the same error as in my repo: ```sh $ yarn install && yarn setup ... $ yarn meta-bump-yarn...

> Seems to me it's more of an alternative to unifile rather than something we could plug in. I was referring to just this part `Vinyl is a very simple...

Also interesting https://www.npmjs.com/package/s3proxy I guess unifile should have an S3 compatible API? We could use https://github.com/minio/minio-js as a client sdk

> I fear we would drift even farther from the Fs API yes that is right the use case I had in mind was the "ls" which now displays all...

Is it better than github's ?