Open Chriscbr opened 2 months ago
It's not always clear when downloading a winglib what targets it supports. Sometimes you might start building an app with the simulator and stumble onto compatibility issues later once you need to deploy to another target.
The README of each published winglib should prominently show what targets it supports. See for example https://www.npmjs.com/package/@winglibs/dynamodb
We store some metadata about the supported targets inside package.json here:
https://github.com/winglang/winglibs/blob/3bab75b50c70af0fc23fa7b5a9d32bc5c0e1de97/dynamodb/package.json#L19-L22
Documentation, Libraries
Makes sense!
Use Case
It's not always clear when downloading a winglib what targets it supports. Sometimes you might start building an app with the simulator and stumble onto compatibility issues later once you need to deploy to another target.
Proposed Solution
The README of each published winglib should prominently show what targets it supports. See for example https://www.npmjs.com/package/@winglibs/dynamodb
Implementation Notes
We store some metadata about the supported targets inside package.json here:
https://github.com/winglang/winglibs/blob/3bab75b50c70af0fc23fa7b5a9d32bc5c0e1de97/dynamodb/package.json#L19-L22
Component
Documentation, Libraries
Community Notes