Hi
Le lun. 24 oct. 2022 à 10:08, Yadd a écrit :
>
> All fixed, only 4/5 packages broken by tsc update itself.
>
Thanks!
J.Puydt
>
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Le dimanche 16 octobre 2022 à 09:37 +0200, Yadd a écrit :
> On 16/10/2022 09:13, julien.pu...@gmail.com wrote:
> > Hi,
> >
> > Le jeudi 13 octobre 2022 à 15:06 +0200, Yadd a écrit :
> > > there are some pending changes (typescript 4.8, rollup 3,
> > > ajv/schema-utils,...). IMO, the more
Hi,
Le jeudi 13 octobre 2022 à 15:06 +0200, Yadd a écrit :
> there are some pending changes (typescript 4.8, rollup 3,
> ajv/schema-utils,...). IMO, the more important is Typescript update
> (rollup 2.19.1 looks able to build rollup-3 packages, schema-utils
> update may break many things).
>
Hi,
I checked whether I could update node-typescript, so I tried many
packages against the new version to see what was broken, then tried
those packages against the current one.
That gives me a list of packages which are indeed broken by the new
version:
node-got
node-merge
Hi,
I uploaded typescript 4.7.4 to experimental.
I know it breaks the following packages:
- node-babel7
- node-got
- node-memfs
- node-ts-jest
I'm going to look into them sometime next week.
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Hi,
I uploaded it to experimental, so we can check whether it breaks
anything.
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Hi,
I wanted to push node-xterm towards version 4, but I saw bug report
#980406 about needing node-node-pty, so I tried my hand on the salsa
repository for this would-be package.
I managed to fix a few things, but I'm stuck on the last hurdle and
upstream is proving pretty uncooperative:
Hi,
Le samedi 26 mars 2022 à 21:11 +0100, Jonas Smedegaard a écrit :
> Quoting julien.pu...@gmail.com (2022-03-26 20:42:45)
> > Le vendredi 25 mars 2022 à 23:22 +0530, Pirate Praveen a écrit :
> > >
> > >
> > > 2022, മാർച്ച് 25 9:21:03 PM IST, julien.pu...@gmail.comൽ എഴുതി
> > > > I prepared
Package: node-recast
Version:
Severity: serious
Tags: ftbfs
Trying to build the package in an unstable sbuild, I get the following
failure:
1) TypeScript
basic printing:
SyntaxError: Initializers are not allowed in ambient contexts.
(2:27)
at instantiate
Package: node-immutable
Version: 4.0.0-2
Severity: serious
Tags: ftbfs
Trying to build the package in an unstable sbuild, I get the following
failure:
+ NODE_PATH=node_modules:/usr/share/nodejs jest --ci
__tests__/ArraySeq.ts
Error
at Function.missingTransform
Package: node-https-proxy-agent
Version: 5.0.0+~cs8.0.0-3
Severity: serious
Tags: ftbfs
Trying to rebuild the package in an unstable sbuild gives the following
failure in upstream test suite:
1) HttpsProxyAgent
"http" module
should receive the 407 authorization code on the
Package: node-ignore
Version: 5.2.0-1
Severity: serious
Tags: ftbfs
Building the package in an unstable sbuild, I get:
ERROR: Coverage for lines (92.3%) does not meet global threshold (100%)
ERROR: Coverage for functions (91.66%) does not meet global threshold
(100%)
ERROR: Coverage for branches
Package: node-configurable-http-proxy
Version: 4.5.0+~cs15.1.4-3
Severity: serious
Tags: ftbfs
Building the package in an unstable sbuild, I get failures:
Randomized with seed 97263
Started
..F...06:23:50.587 [ConfigProxy]
ESC[31merrorESC[39m: 404 GET /nope
06:23:50.860
Package: node-base64url
Version: 3.0.1-7
Severity: serious
Tags: ftbfs
Trying to build the package in an unstable sbuild, the upstream test
suite fails because it doesn't find a 100% coverage:
ERROR: Coverage for lines (97.22%) does not meet global threshold
(100%)
ERROR: Coverage for branches
Package: node-config
Version: 3.3.7-1
Severity: serious
Tags: ftbfs
While rebuilding your package with an unstable sbuild, it failed at six
points in the upstream test suite, with the same error:
» An unexpected error was caught: TypeError: Cannot set
property offset of [object Object]
Le vendredi 25 mars 2022 à 23:22 +0530, Pirate Praveen a écrit :
>
>
> 2022, മാർച്ച് 25 9:21:03 PM IST, julien.pu...@gmail.comൽ എഴുതി
> > Hi,
> >
> > I prepared the package and uploaded it to experimental: I know by
> > experience that an update from 4.5.4 to 4.6.3 has a very high
> > chance to
Le vendredi 25 mars 2022 à 17:34 +0100, Yadd a écrit :
> On 25/03/2022 17:33, Yadd wrote:
> >
> > We're far enough away from Bookworm's release to allow us some
> > build-only FTBFS ;-)
>
> But please wait for nodejs 14 migration before uploading this to
> unstable
Good point!
J.Puydt
--
Hi,
I prepared the package and uploaded it to experimental: I know by
experience that an update from 4.5.4 to 4.6.3 has a very high chance to
break things.
If I'm mistaken and it doesn't bring pain all around, I'll upload to
unstable in two weeks. If I'm right, well, here's a nice thread start
Le jeudi 10 février 2022 à 16:20 +0100, Yadd a écrit :
> On 10/02/2022 15:38, Yadd wrote:
> > Package: node-csstype
> > Version: 3.0.10-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > debian/rules launches `ts-node --files build.ts --start` which
> > (only)
> > modifies
Hi,
Le mar. 18 janv. 2022 à 13:54, Caleb Adepitan a
écrit :
>
> Source: lumino
> Version: 2021.12.13-1
> Severity: important
> Tags: ftbfs
> User: pkg-javascript-devel@alioth-lists.debian.net
> Usertags: webpack5
>
> We are starting to build against webpack5 in experimental and the
> package
Hi,
Le lundi 17 janvier 2022 à 16:15 +0100, Caleb Adepitan a écrit :
>
> I just updated the lumino package from 2021.12.13-1 to 2021.12.13-2.
> Which fixes one of the bugs encountered when reverse building with
> webpack 5. Here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003884.
>
Le mer. 29 déc. 2021 à 18:17, Yadd a écrit :
>
> I propose to remove them. If someone later wants to package the new
> packages with their new names, feel free of course.
>
> OK for you ?
>
Yes
J. Puydt
>
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hi,
Le vendredi 24 décembre 2021 à 19:00 +0100, Yadd a écrit :
>
> you were wrong in your fix: you wanted
> mdn-browser-compat-data/html/global_attributes.json which is provided
> by mdn-browser-compat-data module (not packaged).
>
> The new @mdn/browser-compat-data provides just one data.json.
Hi,
I wanted to update node-typescript from 4.5.2 to 4.5.3.
As usual, I test my new package on a few rdeps before uploading. This
time I saw it broke ts-node and node-rollup-plugin-typescript. The
problem is that when I reverted to 4.5.2, I got the same failures... so
the new package might not
Hi,
Le samedi 11 décembre 2021 à 13:24 +0100, Yadd a écrit :
>
> echo -n require > debian/tests/pkg-js/SKIP
Good one!
How does one test an import-able module?
J.Puydt
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Le vendredi 10 décembre 2021 à 15:07 +0100, Jonas Smedegaard a écrit :
>
> It is better to embed uscan-tracked than embed without tracking, even
> if embedding an older version. That way uscan (and e.g. tracker.d.o)
> helps remind us to upgrade when possible.
I agree it's better ; but the
Package: node-browserslist
Version: 4.18.1+~cs5.1.2-1
I needed picocolors for another package, and didn't find it was
embedded in this package ; now that it's packaged, it would be nice to
unembed it.
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Le vendredi 10 décembre 2021 à 12:57 +0100, Jonas Smedegaard a écrit :
> Quoting Julien Puydt (2021-12-10 09:27:30)
> > Le jeudi 09 décembre 2021 à 17:16 +0100, Jonas Smedegaard a écrit :
> > > Perhaps the package simply has not yet entered Debian¹ at all?
>
Hi,
Le vendredi 10 décembre 2021 à 14:09 +0100, Yadd a écrit :
>
> I think you can safely drop this file: csso-browser.js isn't used by
> svgo.
I just dropped things left and right ; indeed it still seems to work.
> But having unupdated modules in debian/node_modules that are
> installed isn't
Hi,
Le jeudi 09 décembre 2021 à 17:16 +0100, Jonas Smedegaard a écrit :
> Quoting Julien Puydt (2021-12-09 17:05:57)
> > Hi,
> >
> > on salsa we have a node-svgo, and the changelog shows traces of
> > having
> > been uploaded to unstable ; but I don't find
Hi,
on salsa we have a node-svgo, and the changelog shows traces of having
been uploaded to unstable ; but I don't find the package in NEW and
can't install it.
What's amusing is that if you have a look at "npm2deb svgo", you'll see
there is no Debian package, but "npm2deb depends svgo" will
Hi,
I wanted to update node-ast-types to the latest upstream, so I prepared
the package. As usual, I tested it with a few rdeps ; and I hit a
strange problem with node-recast.
So I tried without the new node-ast-types, and it's still the same:
Get:1 http://ftp.fr.debian.org/debian unstable/main
Le mardi 30 novembre 2021 à 23:25 +0100, Jonas Smedegaard a écrit :
>
>
> Sorry, let me clarify:
>
> This command:
>
> apt-cache show node-lodash-packages |grep Version
>
> does not reliably tell you if TypeScript definitions are provided, so
> is
> dependent on someone telling you which
Le dimanche 28 novembre 2021 à 17:30 +0100, Jonas Smedegaard a écrit :
> Quoting Julien Puydt (2021-11-28 17:01:56)
> > Le dimanche 28 novembre 2021 à 15:38 +0100, Yadd a écrit :
> > >
> > > please try with node-lodash-packages
> > > 4.17.21+dfsg+~cs8
Le dimanche 28 novembre 2021 à 15:38 +0100, Yadd a écrit :
>
> please try with node-lodash-packages 4.17.21+dfsg+~cs8.31.198.20210220-
> 2
> from experimental.
I don't see it yet:
apt-cache show node-lodash-packages |grep Version
Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
but I'll give it a
Package: node-mdn-browser-compat-data
Version: 4.0.12-1
The package doesn't ship some parts of upstream ; I'm trying to package
a module and get:
Error: Cannot find module 'mdn-browser-compat-
data/html/global_attributes.json'
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Package: node-react
Version: 17.0.2+dfsg+~cs106.66.56-1
Severity: wishlist
Please ship TypeScript definitions, as they're needed on the way to
jupyterlab -- especially for react and react-dom as far as I can tell.
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Package: node-marked
Version: 0.8.0+ds+repack-3
Severity: minor
Please ship the TypeScript definitions ; they're needed on the way to
jupyterlab.
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Package: node-lodash
Version: 4.17.21+dfsg+~cs8.31.196.20210220-2
Severity: minor
Please ship TypeScript definitions, in particular for lodash.escape, as
I'm finding I need them on the way to jupyterlab.
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Package: node-glob
Version: 7.1.7+~cs7.5.19-2
Severity: wishlist
I found a package wanting fast-glob for a single call to sync... glob
would be a nice replacement if it had TypeScript declarations.
Thanks,
J.Puydt
--
Pkg-javascript-devel mailing list
Hi,
Le samedi 27 novembre 2021 à 09:24 +0100, Yadd a écrit :
>
> This is a known typescript bug, it is unable to use nodejs paths. To
> workaround, use this:
>
> $ cat > debian/nodejs/extlinks << EOF
> setimmediate
> @types/node
> EOF
How does that work?
Thanks,
J.Puydt
--
Package: node-lumino
Version: 2021.11.4-1
Severity: normal
X-Debbugs-CC: Debian Javascript Maintainers
There are errors when compiling @lumino/polling:
src/poll.ts(18,7): error TS2304: Cannot find name 'setImmediate'.
src/poll.ts(26,7): error TS2304: Cannot find name 'clearImmediate'.
and
Package: node-minimist
Version: 1.2.5+~cs5.3.2-1
Severity: wishlist
That will make the module available from TypeScript modules.
Thanks,
J.Puydt
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Package: node-url-parse
Version: 1.5.3-1
Severity: wishlist
That will make the module available from TypeScript modules.
Thanks,
J.Puydt
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hi,
Le dimanche 21 novembre 2021 à 14:18 +0100, Yadd a écrit :
> Le 21/11/2021 à 09:11, Andrius Merkys a écrit :
>
> >
> > I must admit my knowledge of JS packaging lags quite a lot, thus I
> > rely
> > a lot on tools. I would expect npm2deb to produce initial packaging
> > at a
> > fair state,
Package: yarnpkg
Version: 1.22.10+~cs22.25.14-4
Severity: wishlist
Updating ts-node would require @yarnpkg/fslib -- can you add it to the
yarnpkg package?
Thanks,
J.Puydt
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Le jeudi 11 novembre 2021 à 16:46 +0100, Jonas Smedegaard a écrit :
>
> I am unsure, however, which release of TypeScript definitions
> corresponds to which version of emscripten, and I fail to locate
> anywhere such relationship is declared.
>
> Would you happen to know where to look for such
Package: emscripten
Version: 2.0.26~dfsg-4
Severity: wishlist
I would need the TypeScript type definitions for emscripten for another
package. They can be found here:
https://www.npmjs.com/package/@types/emscripten
Can you add them to the emscripten package?
Thanks,
J.Puydt
--
Hi
Le ven. 15 oct. 2021 à 17:39, Yadd a écrit :
> next uscan version will (probably) fail when filenamemangle fails.
>
Why will it fail?
J.Puydt
>
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hi,
RGI_Emoji was added to upstream in october 2020, so indeed in march
2021, you saw it upstream and this package hadn't it.
Now 14.0.0 is out, I propose to wait for a new unicode-data package,
and then update node-unicode-data to use it.
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Hi,
after more poking around, there were two issues:
1) the smaller one was that TypeScript >= 4.4 breaks upstream, but I
could write a patch (and forward it) ;
2) the bigger one is that we need a more recent node-tslib, which is
only in experimental at the moment, so I'm only uploading the
Hi,
updating to a newer version will probably make that issue go away ; I'm
expecting an answer to https://github.com/jupyterlab/lumino/issues/235
before going forward.
Cheers,
J.Puydt
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Le lundi 13 septembre 2021 à 11:18 +0200, Jonas Smedegaard a écrit :
>
> (3) upload conservatively only to experimental until A and B and C
> are
> aligned, possible through our nudging upstream to make the needed
> changes, and possible through applying dirty patches (preferrably at
> the
Le dimanche 12 septembre 2021 à 20:30 +0200, Yadd a écrit :
> You'll notice that I didn't fault anyone, I just tried not to let
> other groups get stuck with our updates. I think I did something
> clean that avoids breaking other packages until nodejs is updated
> and keeps the upstream format.
Hi
Le dim. 12 sept. 2021 à 18:39, Yadd a écrit :
> Le 12/09/2021 à 18:35, Pirate Praveen a écrit :
> >
> > With nodejs supporting ESM natively, we should try to avoid as much of
> > build steps as possible.
>
> You're right, but for now this avoid to downgrade updated packages (like
>
Hi,
I tried to update the above-mentioned package and pushed quite a few
changes but:
- it looks like the orig tarball generation is quite strange, with a
succession of "Files-Excluded: *" and "Files-Included: very short list"
which confuses both dpkg-source and lintian -- and there's no +dfsg
Package: webpack
Version: 5.6.0+~cs6.4.0-1~exp2
Severity: grave
I was trying to update another js-team package and couldn't understand
what was wrong until I tried to just run webpack by itself in another
directory:
$ webpack
[webpack-cli] ReferenceError: options is not defined
at
Package: node-strip-json-comments
Version: 4.0.0-1
Severity: serious
I have to drop dont_be_a_module.patch ; it's too dirty. I'll do it
later today, but still want to prevent any migration to testing.
J.Puydt
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Le vendredi 27 août 2021 à 12:20 +0200, Yadd a écrit :
> use `echo require > debian/tests/pkg-js/SKIP` for such modules.
That makes a node-something package not try to require itself as part
of the autopkgtest-ing ; but I don't think that answers my question.
The current upstream version of
Hi,
I updated the node-strip-json-comments package ; it required refreshing
the existing patch (porting upstream test suite to a framework we
have), which was pretty normal, but also, and I find it annnoying, a
new one.
The upstream package.json declares it's a JS module, so it can't be
Package: node-get-stream
Version: 4.1.0-1
Severity: wishlist
The newest ts-node wants the TypeScript definitions for this package ;
and it looks like upstream does ship them now so updating to the newest
version should make this issue disappear.
Cheers,
JP
--
Pkg-javascript-devel mailing list
Hi,
I'm stuck also with missing types for pretty-format, and it's from the
jest package too.
My main goal is jupyterlab. Some parts of it want typestyle, but that
needs csstype and free-style.
For csstype, I need types for the 'jest' module ; and for free-style
for 'pretty-format' and
Package: node-chalk
Version: 2.4.2-1
Severity: wishlist
I need much more recent versions to package other things.
Cheers,
JP
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Package: jest
Version: 26.6.3+ds+~cs64.27.30-1
The file /usr/share/nodejs/package.json says the TypeScript definitions
are available in build/jest.d.ts, but the package doesn't contain that
file : the build/ directory only has jest.js.
Cheers,
JP
--
Pkg-javascript-devel mailing list
Hi,
I advanced quite well since this morning, so right now getting node-
rimraf up to date and with definitions is on the top of my todo list.
I'll work locally at first, but will probably upload in a few days,
unless it's a problem for you?
Cheers
--
Pkg-javascript-devel mailing list
Hi Jonas,
you have uploaded 4.0.1 to experimental in august 2019 ; is there a
reason why it didn't get into unstable?
I ask because I want to work on shipping the TypeScript types with the
package... and the definition are for v4.
So basically, I want to work on the package, but don't want to
Package: node-proxyquire
Version: 2.1.3+~1.0.1+~1.0.2-10
Severity: minor
From the package's tracker :
The VCS repository is not up to date, push the missing commits. high
vcswatch reports that the current version of the package is not in its
VCS.
Either you need to push your commits and/or your
Package: node-diff
Version: 1.4.0~dfsg-4
Severity: wishlist
please ship TypeScript definitions for diff ; upstream might not
provide them yet, but they are already used by ts-node, which I would
like to package on my way to JupyterLab.
You can find them here:
Package: node-rimraf
Version: 2.6.3-1
Severity: wishlist
please ship TypeScript definitions with node-rimraf ; upstream might
not include them yet, but some are available here:
https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/rimraf
and they are used in ts-node, which I would
Le mardi 10 novembre 2020 à 06:34 +0100, Xavier a écrit :
> Done
Thanks!
JP
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Le lundi 09 novembre 2020 à 21:08 +, Sudip Mukherjee a écrit :
> I have attached the list.
> Do you want me to add them in my MBF list and raise bug reports for
> them?
If I remember well, I'm the main culprit behind those, and I'll refresh
them -- probably at the end of the week:
Le mardi 10 novembre 2020 à 06:16 +0100, Xavier a écrit :
>
> node-react contains already @types/react, which other types do you
> need?
Ah, sorry, I hadn't understood your question. I get complaints about
not finding definitions for react-dom.
Thanks,
JP
--
Pkg-javascript-devel mailing list
Le lundi 09 novembre 2020 à 20:06 +0100, Xavier a écrit :
> Hi, which ones ?
Well, jupyterlab only says it needs definitions, but not where to find
them, so if upstream doesn't provide them, I would say:
https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/react
JP
--
Package: node-react
Version: 17.0.1+dfsg+~cs32.23.54-3
Severity: wishlist
Please ship TypeScript definitions for react : I'm trying to package
jupyterlab, and some of its packages depend on those.
Thanks,
JP
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Package: node-json5
Version: 2.1.3-1
Severity: wishlist
Please ship typescript definitions within the package.
Upstream hasn't them yet: https://github.com/json5/json5/issues/235
But some are available from here already:
Package: pkg-js-tools
Version: 0.9.45
Severity: wishlist
As discussed in #973983, it might be a good idea to make sure pkg-js-
tools adds the main component to ${nodejs:Provides} when that component
isn't the package name.
Cheers,
JP
--
Pkg-javascript-devel mailing list
Le dimanche 08 novembre 2020 à 19:07 +0100, Xavier a écrit :
> Le 08/11/2020 à 18:53, Julien Puydt a écrit :
> > Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit :
> > > did you try to set onne of them in debian/nodejs/main ?
> >
> > Oh, dear... putting
Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit :
> did you try to set onne of them in debian/nodejs/main ?
Oh, dear... putting one of them in there did make things go through,
but checking the resulting package : all the other components ended up
in a node_modules directory within the
Hi,
Le dimanche 08 novembre 2020 à 16:25 +0100, Xavier a écrit :
> Le 08/11/2020 à 16:02, Julien Puydt a écrit :
> > Package: pkg-js-tools
> > Version: 0.9.45
> >
> > I'm trying to package lumino (ITP 972487), which has a pretty
> > special
> > struc
Package: pkg-js-tools
Version: 0.9.45
I'm trying to package lumino (ITP 972487), which has a pretty special
structure:
- no main module ;
- only packages.
My d/control has a build dep on pkg-js-tools, and uses "Provides:
${nodejs:Provides}" ; I have a d/nodejs/additional_components with
Package: wnpp
Severity: wishlist
X-Debbugs-CC: pkg-javascript-de...@lists.alioth.debian.org
* Package name: lumino
Version: 0~20200824+git93880412-1
Upstream author: Jupyter Project contributors
* URL: https://github.com/jupyterlab/lumino
License: BSD-3-clause
Description: large set of libraries
Package: node-websocket
Version: 1.0.31-1
Severity: wishlist
Please add the typescript type definitions to the package ; either
coming from upstream or from
https://github.com/DefinitelyTyped/DefinitelyTyped
Thanks,
JP
--
Pkg-javascript-devel mailing list
Package: libjs-codemirror
Version: 5.57.0-1
Severity: wishlist
The current package doesn't ship typescript type definitions -- please
add them ; either from upstream or from
https://github.com/DefinitelyTyped/DefinitelyTyped
Thanks,
JP
--
Pkg-javascript-devel mailing list
Hi,
my first goal was to update nbconvert -- but it needs a more recent
nbsphinx.
So I have a look at nbsphinx. Ah, it requires a more recent ipywidgets.
Now ipywidgets gets interesting : that package suffers from a lack of
love, for reasons made obvious below.
The purely Python part is ok,
Package: node-sinon
Version: 9.0.1+ds-1
Please add the type definitions from DefinitelyTyped to the package ;
both direct :
https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/sinon
and indirect :
Package: node-braces
Version: 3.0.2-2
Please add typescript type definitions from DefinitelyTyped to the
package:
https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/braces
Thanks,
JP
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Package: node-jsdom
Version: 16.2.2+~cs56.12.24-1
Please add the type definitions for parse5 from DefinitelyTyped to the
package:
https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/parse5
Thanks,
JP
--
Pkg-javascript-devel mailing list
Package: node-tough-cookie
Version: 3.0.0-1
Please add the type definitions from DefinitelyTyped to the package :
https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/tough-cookie
Cheers,
JP
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Ok, I dug some more, and found the package lacks (first level) :
- @types/parse5 and @types/tough-cookie for @types/lodash
- @types/braces for @types/micromatch
- @types/sinonjs__fake-timers for @types/sinon
and I checked on DefinitelyTyped's repository that there are no higher
level deps :
Package: node-typescript-types
Version: 20200808-1
Severity: important
I'm trying to update the node-ast-types packages, but fail for various
reasons ; one of them is that node-typescript-types ships
@types/micromatch which depends on @types/braces, but doesn't ship
@types/braces.
I checked that
Package: node-tslib
Version: 1.11.2-1
Upstream released 2.0.1, and node-ast-types requires that version ; can
you package it?
Thanks,
JP
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hi,
node-magic-string has a FTBFS bug because the build dep on rollup at
least version 1 isn't satisfiable - that's not the case anymore, so I
decided to give it a go.
It turns out the new upstream version breaks two tests in node-buble
(but not the other depends of node-magic-string - I
Hi,
Le lundi 24 février 2020 à 23:28 +0100, Bastien ROUCARIES a écrit :
> With newer pkg-js-tools we must embded the types is not supplied by
> the main package as a compoent of the main package.
I have no clue how components work for Debian package. Where can I read
about it?
JP
--
Hi,
upstream is up to 1.28.0 ; Debian unstable has only 0.68.2,
experimental has 1.10.1.
A number of rollup-plugin-foos need at least version 1 to build, and
quite a few of them have been merged into a single repository here :
https://github.com/rollup/plugins
Why is the newer rollup only in
Le mardi 29 octobre 2019 à 12:45 +0100, Xavier a écrit :
> Control: reassign -1 node-typescript
>
> Le 29/10/2019 à 08:29, Julien Puydt a écrit :
> > Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit :
> > > Hi JS team,
> > >
> > &
Le mardi 29 octobre 2019 à 07:49 +0100, Xavier a écrit :
> Hi JS team,
>
> why did node-typescript have such link ?
>
> /usr/share/nodejs/tslib -> typescript/lib
>
> This creates this conflict.
>
Well, isn't node-typescript supposed to provide that lib?
JP
--
Pkg-javascript-devel mailing
Le mardi 22 octobre 2019 à 14:25 +0530, Pirate Praveen a écrit :
> I don't think that is right characterization. NEW queue is not same
> for all packages, javascript packages are treated differently from
> other languages. ruby packages get cleared in days or maximum weeks.
> Also ftp masters
Le mardi 22 octobre 2019 à 10:01 +0200, Xavier a écrit :
> Le Mardi, Octobre 22, 2019 09:10 CEST, Julien Puydt <
> julien.pu...@laposte.net> a écrit:
> > If you want to have ts-node, why not package it properly, with a
> > RFP or
> > ITP?
> >
> >
If you want to have ts-node, why not package it properly, with a RFP or
ITP?
I don't see the point into packaging those together...
JP
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Le mercredi 02 octobre 2019 à 07:12 +0200, Xavier a écrit :
> Hi all,
>
> when trying to update node-css-what, it's OK with testing but
> unstable
> give me this:
>
> tsc
> error TS2318: Cannot find global type 'Array'.
> error TS2318: Cannot find global type 'Boolean'.
> error TS2318: Cannot
1 - 100 of 124 matches
Mail list logo
