An idea suggested by @anmonteiro: have the plugin generate a package.json file, or extend the one existing already. This should be fairly easy by leveraging existing esy libraries —that the project already vendors— to deal with this kind of json files.
An idea suggested by @anmonteiro: have the plugin generate a
package.json
file, or extend the one existing already. This should be fairly easy by leveraging existing esy libraries —that the project already vendors— to deal with this kind of json files.