[Pkg-javascript-devel] @rollup/* plugins

[Xavier]

Le 16/09/2020 à 19:24, Xavier a écrit :
> Le 15/09/2020 à 18:35, Xavier a écrit :
>> Le 15/09/2020 à 17:04, Pirate Praveen a écrit :
>>>
>>>
>>> On Tue, Sep 15, 2020 at 11:06, Xavier <yadd at debian.org> wrote:
>>>> Hi all,
>>>>
>>>> next node-babel7 needs some @rollup/* plugins that can not be replaced
>>>> by rollup-*.
>>>> Proposition: for each node-rollup-* package:
>>>>  * change default debian/watch entry to download @rollup/*
>>>>  * embed old rollup-* as a component to keep compatibility
>>>>    *OR*
>>>>  * create a dummy rollup-* module with
>>>>      `module.export = require("@rollup/NAME")`
>>>>
>>>> Do you agree with that?
>>>>
>>>> NB: @rollup/* look to work fine with current rollup
>>>
>>> I think all @rollup/plugins are in a single repo. Does it make sense to
>>> create a single rollup-plugins package?
>>
>> Yes single repo but:
>>  * no version management
>>  * no tags
>>
>> So uscan won't be able to know what version it downloads and if it's a
>> release or not
> 
> I prepared an upgrade of node-rollup-pluginutils which contains both
> @rollup/pluginutils and rollup-pluginutils (pushed to salsa only). This
> package can be built using current (legacy) modules and future ones (see
> debian/rules).
> 
> debian/watch downloads github.com/rollup/plugins content based on tags
> named "pluginsutils-v<version>".
> 
> I think that this can be reproduced for each node-rollup-* package and I
> don't find a better way for now.
> 
> Could you take a look ?

I pushed some rollup-plugin* to experimental. They provides legacy +
up-to-date module. Hope someone could have a look