Shahar Talmi
Shahar Talmi
@filiptronicek did you try to package the latest version? any packaging issue should be resolved in v3 and up
You also need to run `npm test`
Try `vsce package --no-dependencies`
I added a build command to make this process easier, all you need to do is clone the repo and then run: ``` $ npm install $ npm run build...
Pull request is welcome On Aug 26, 2016 1:11 AM, "sikorsky555" [email protected] wrote: > — > You are receiving this because you are subscribed to this thread. > Reply to...
Not sure I follow. If I understand correctly, the second `setManifestGenerator` function is part of app A, so how come it doesn't know app A's (its own) name?
I'm not sure I understand. If a widget requires more files, why can't you list those files in the manifest generator in the hosting app?
Why not do just: ``` js widgetsProvider.setManifestGenerator(function () { return function (name) { if (name === 'specialWidget') return {...}; else return {...}; }; }); ``` Multiple generators is also supported...
Of course, you should aspire to have a generic manifest. Still I don't think that a special API is needed for "specific" manifests since the following code: ``` js widgetsProvider.setManifestGenerator(function...