Re: [Pkg-javascript-devel] JS roadmap for Debian 12
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
Re: [Pkg-javascript-devel] JS roadmap for Debian 12
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 important is Typescript > > > update > > > (rollup 2.19.1 looks able to build rollup-3 packages, schema- > > > utils > > > update may break many things). > > > > > > Are you OK ? Is someone able to launch a massive rebuild for > > > typescript reverse dependencies ? > > > > > > Concerning node-typescript, I haven't updated it in unstable for a > > while: > > (1) a few of depending packages are broken even without updating it > > ; > > (2) updating it would break a bunch of others ; > > (3) I'm a bit short on time for JS packages these days to fix all > > of > > those. > > > > I still pushed to experimental, explaining what I had seen broken. > > > > I'll do a test-run locally to write new lists of (1) and (2): it > > doesn't take that much time. [Or more precisely, much of my time! > > My > > box does work for hours...] > > > > I get the initial list of packages using: > > ssh mirror.ftp-master.debian.org "dak rm -Rn node-typescript" > > so hopefully the above lists are complete. > > > > Cheers, > > > > J.Puydt > > Hi, > > I fixed a lot of previously broken things this month. I thinks JS > packages are now in a good state and we can update typescript and see > what is broken on next massive rebuild. > So if Team agrees, let's upload typescript 4.8 to unstable. I compiled many things with the new node-typescript, and the failing ones are: ipywidgets node-cheerio node-configurable-http-proxy node-domhandler node-fetcha node-got node-htmlparser2 node-jest node-js-chardet node-jsdom node-lib0 node-memfs node-merge node-mermaid node-nouislider node-rollup-plugin-typescript2 node-route-recognizer node-yargs node-yjs node-y-websocket node-zkochan-cmd-shim If I try to compile the packages from this list with the current node- typescript, I get the list of already failing: ipywidgets node-cheerio node-configurable-http-proxy node-domhandler node-fetcha node-htmlparser2 node-jest node-js-chardet node-memfs node-mermaid node-nouislider node-route-recognizer node-zkochan-cmd-shim which makes a difference only for: node-got node-lib0 node-rollup-plugin-typescript2 node-yargs node-yjs node-y-websocket so I would say the sensible plan is to first fix those six broken by the new version ; and then upload the new version. 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
Re: [Pkg-javascript-devel] JS roadmap for Debian 12
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). > > Are you OK ? Is someone able to launch a massive rebuild for > typescript reverse dependencies ? Concerning node-typescript, I haven't updated it in unstable for a while: (1) a few of depending packages are broken even without updating it ; (2) updating it would break a bunch of others ; (3) I'm a bit short on time for JS packages these days to fix all of those. I still pushed to experimental, explaining what I had seen broken. I'll do a test-run locally to write new lists of (1) and (2): it doesn't take that much time. [Or more precisely, much of my time! My box does work for hours...] I get the initial list of packages using: ssh mirror.ftp-master.debian.org "dak rm -Rn node-typescript" so hopefully the above lists are complete. 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
[Pkg-javascript-devel] Updating node-typescript
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 node-rollup-plugin-sass node-rollup-plugin-typescript node-yargs node-yjs node-y-websocket some of them are in their latest upstream version, so there's not even this reason to explain the failure... I uploaded this version to experimental, like the previous ones. 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
[Pkg-javascript-devel] Updating typescript
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-typescript 4.7.3
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
[Pkg-javascript-devel] Improving node-node-pty towards node-xterm version 4
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: https://github.com/microsoft/node-pty/issues/539 Question: isn't src/windowsPtyAgent.ts just for the windows port of the lib, in which case it can somehow be dropped? If anybody has any answer or hint, don't hesitate... 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
Re: [Pkg-javascript-devel] Updating node-typescript to 4.6.3
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 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 to notify and discuss. > > > > > > Please rebuild the reverse build dependencies using a tool like > > > ratt, salsa ci script created by Jeremy or > > > salsa.debian.org/ruby-team/meta script. > > > > I did t by hand: > > Great. > > [ breakage details snipped ] > > Now please file proper bugreports against each failing package! Here is the current status, giving either the bug number in Debian or the upstream report: * Culprit (fails with new node-typescript only) ** lumino (https://github.com/jupyterlab/lumino/issues/298) Compiling datagrid src/graphicscontext.ts(243,7): error TS2322: Type 'string' is not assignable to type 'GlobalCompositeOperation * Innocent (same error with old and new node-typescript) ** ipywidgets (#1008328) ModuleNotFoundError: No module named 'ipython_genutils' ** jupyter-notebook (#1008422) ERROR in ./node_modules/postcss/lib/map-generator.js Module not found: Error: Can't resolve './../../../buffer' in '/<>/node_modules/postcss/lib' ** node-recast (#1008515) 1) TypeScript basic printing: SyntaxError: Initializers are not allowed in ambient contexts. (2:27) at instantiate (node_modules/@babel/parser/src/parse- error/credentials.js:61:22) at toParseError (node_modules/@babel/parser/src/parse- error.js:58:12) at Object.raise (node_modules/@babel/parser/src/tokenizer/index.js:1763:19) 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
[Pkg-javascript-devel] Bug#1008515: FTBFS in the upstream test suite
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 (node_modules/@babel/parser/src/parse- error/credentials.js:61:22) at toParseError (node_modules/@babel/parser/src/parse- error.js:58:12) at Object.raise (node_modules/@babel/parser/src/tokenizer/index.js:1763:19) at Object.parseVarStatement (node_modules/@babel/parser/src/plugins/typescript/index.js:2566:16) at Object.parseStatementContent (node_modules/@babel/parser/src/parser/statement.js:391:21) at Object.parseStatementContent (node_modules/@babel/parser/src/plugins/typescript/index.js:2603:20) at Object.parseStatement (node_modules/@babel/parser/src/parser/statement.js:329:17) at Object.parseExportDeclaration (node_modules/@babel/parser/src/parser/statement.js:2123:17) at Object.parseExportDeclaration (node_modules/@babel/parser/src/plugins/typescript/index.js:2843:15) at Object.maybeParseExportDeclaration (node_modules/@babel/parser/src/parser/statement.js:2062:31) at Object.parseExport (node_modules/@babel/parser/src/parser/statement.js:1982:29) at Object.parseExport (node_modules/@babel/parser/src/plugins/typescript/index.js:2510:22) at Object.parseStatementContent (node_modules/@babel/parser/src/parser/statement.js:431:25) at Object.parseStatementContent (node_modules/@babel/parser/src/plugins/typescript/index.js:2603:20) at Object.parseStatement (node_modules/@babel/parser/src/parser/statement.js:329:17) at Object.parseBlockOrModuleBlockBody (node_modules/@babel/parser/src/parser/statement.js:1078:25) at Object.tsParseModuleBlock (node_modules/@babel/parser/src/plugins/typescript/index.js:1722:12) at Object.tsParseModuleOrNamespaceDeclaration (node_modules/@babel/parser/src/plugins/typescript/index.js:1749:26) at Object.tsParseDeclaration (node_modules/@babel/parser/src/plugins/typescript/index.js:2000:25) at cb (node_modules/@babel/parser/src/plugins/typescript/index.js:1919:23) at Object.tsInAmbientContext (node_modules/@babel/parser/src/plugins/typescript/index.js:3502:16) at Object.tsTryParseDeclare (node_modules/@babel/parser/src/plugins/typescript/index.js:1868:19) at Object.tsParseExpressionStatement (node_modules/@babel/parser/src/plugins/typescript/index.js:1940:36) at Object.parseExpressionStatement (node_modules/@babel/parser/src/plugins/typescript/index.js:2744:18) at Object.parseStatementContent (node_modules/@babel/parser/src/parser/statement.js:477:19) at Object.parseStatementContent (node_modules/@babel/parser/src/plugins/typescript/index.js:2603:20) at Object.parseStatement (node_modules/@babel/parser/src/parser/statement.js:329:17) at Object.parseBlockOrModuleBlockBody (node_modules/@babel/parser/src/parser/statement.js:1078:25) at Object.parseBlockBody (node_modules/@babel/parser/src/parser/statement.js:1054:10) at Object.parseProgram (node_modules/@babel/parser/src/parser/statement.js:214:10) at Object.parseTopLevel (node_modules/@babel/parser/src/parser/statement.js:197:25) at Object.parse (node_modules/@babel/parser/src/parser/index.js:41:10) at Object.parse (node_modules/@babel/parser/src/plugins/typescript/index.js:3581:20) at Object.parse (node_modules/@babel/parser/src/index.js:58:38) at Object.parse (parsers/typescript.js:17:27) at Object.parse (lib/parser.js:23:30) at check (test/typescript.ts:19:26) at Context. (test/typescript.ts:276:5) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10) at /usr/share/nodejs/mocha/lib/runner.js:801:12 at next (/usr/share/nodejs/mocha/lib/runner.js:593:14) at /usr/share/nodejs/mocha/lib/runner.js:603:7 at next (/usr/share/nodejs/mocha/lib/runner.js:486:14) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5) at processImmediate (internal/timers.js:464:21) 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
[Pkg-javascript-devel] Bug#1008514: FTBFS -- upstream test suite failure
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 (/usr/share/nodejs/buble/dist/buble.cjs.js:367:9) at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:2650:17) at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:105:11) at /usr/share/nodejs/buble/dist/buble.cjs.js:103:40 at Array.forEach () at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:103:11) at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:105:11) at Node.initialise (/usr/share/nodejs/buble/dist/buble.cjs.js:2118:9) at /usr/share/nodejs/buble/dist/buble.cjs.js:795:34 dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 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
[Pkg-javascript-devel] Bug#1008512: FTBFS in upstream test suite
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 `http.ClientResponse`: Uncaught Error [ERR_SOCKET_CLOSED]: Socket is closed at new NodeError (internal/errors.js:322:7) at Socket._writeGeneric (net.js:789:8) at Socket._write (net.js:811:8) at doWrite (internal/streams/writable.js:377:12) at clearBuffer (internal/streams/writable.js:529:7) at Socket.Writable.uncork (internal/streams/writable.js:317:7) at ClientRequest._flushOutput (_http_outgoing.js:935:10) at ClientRequest._flush (_http_outgoing.js:904:22) at onSocketNT (_http_client.js:824:9) at processTicksAndRejections (internal/process/task_queues.js:83:21) 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
[Pkg-javascript-devel] Bug#1008513: FTBFS unsufficient coverage
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 (87.65%) does not meet global threshold (100%) ERROR: Coverage for statements (92.08%) does not meet global threshold (100%) --|-|--|-|-|--- -- File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s --|-|--|-|-|--- -- All files | 92.08 |87.65 | 91.66 |92.3 | index.js | 92.08 |87.65 | 91.66 |92.3 | 364,369,377,382- 383,419-421,562,569 --|-|--|-|-|--- -- 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
[Pkg-javascript-devel] Bug#1008511: FTBFS failures in the upstream test suite
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 [ConfigProxy] ESC[31merrorESC[39m: 503 GET /missing/prefix connect ECONNREFUSED 127.0.0.1:54321 ...06:23:50.953 [ConfigProxy] ESC[31merrorESC[39m: 404 GET /nope 06:23:51.227 [ConfigProxy] ESC[31merrorESC[39m: 503 GET /missing/prefix connect ECONNREFUSED 127.0.0.1:54321 .06:23:51.270 [ConfigProxy] ESC[31merrorESC[39m: 503 GET /missing/prefix connect ECONNREFUSED 127.0.0.1:54321 06:23:51.273 [ConfigProxy] ESC[31merrorESC[39m: 503 GET /missing/ws connect ECONNREFUSED 127.0.0.1:54321 ...06:23:51.346 [ConfigProxy] ESC[31merrorESC[39m: 404 GET /foo/bar ...06:23:51.370 [ConfigProxy] ESC[31merrorESC[39m: 500 GET /% URIError: URI malformed at decodeURIComponent () at ConfigurableProxy.targetForReq (/<>/lib/configproxy.js:385:27) at ConfigurableProxy.handleProxy (/<>/lib/configproxy.js:529:17) at ConfigurableProxy.handleProxyWeb (/<>/lib/configproxy.js:613:17) at Server. (/<>/lib/configproxy.js:198:27) at Server.emit (events.js:400:28) at parserOnIncoming (_http_server.js:900:12) at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17) .06:23:51.403 [ConfigProxy] ESC[32minfoESC[39m: Adding route / -> http://127.0.0.1:9001 06:23:51.403 [ConfigProxy] ESC[32minfoESC[39m: Route added / -> http://127.0.0.1:9001 . Failures: 1) CLI Tests custom-header Message: Error: Timeout - Async function did not complete within 1ms (set by jasmine.DEFAULT_TIMEOUT_INTERVAL) Stack: at at listOnTimeout (internal/timers.js:557:17) at processTimers (internal/timers.js:500:7) Message: Error: Timeout - Async function did not complete within 1ms (set by jasmine.DEFAULT_TIMEOUT_INTERVAL) Stack: at at listOnTimeout (internal/timers.js:557:17) at processTimers (internal/timers.js:500:7) 58 specs, 1 failure 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
[Pkg-javascript-devel] Bug#1008510: FTBFS unsufficient coverage
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 (75%) does not meet global threshold (100%) ERROR: Coverage for statements (94.73%) does not meet global threshold (100%) ---|-|--|-|-|-- - File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s ---|-|--|-|-|-- - All files | 94.73 | 75 | 100 | 97.22 | node-base64url-3.0.1 | 100 | 100 | 100 | 100 | index.js | 100 | 100 | 100 | 100 | node-base64url-3.0.1/dist | 94.44 | 75 | 100 | 97.05 | base64url.js | 95.23 |83.33 | 100 | 100 | 13 pad-string.js| 93.33 | 50 | 100 | 93.33 | 8 ---|-|--|-|-|-- - 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
[Pkg-javascript-devel] Bug#1008509: FTBFS - six upstream tests failing
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] which has only a getter 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
Re: [Pkg-javascript-devel] Updating node-typescript to 4.6.3
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
> > 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
> > to notify and discuss.
>
> Please rebuild the reverse build dependencies using a tool like ratt,
> salsa ci script created by Jeremy or salsa.debian.org/ruby-team/meta
> script.
I did t by hand:
* Culprit (fails with new node-typescript only)
** lumino
Compiling datagrid
src/graphicscontext.ts(243,7): error TS2322: Type 'string' is not
assignable to type 'GlobalCompositeOperation
** node-ampproject-remapping
src/resolve.ts(1,24): error TS2307: Cannot find module
'@jridgewell/resolve-uri' or its corresponding type declarations.
src/trace-mapping.ts(1,32): error TS2307: Cannot find module
'@jridgewell/sourcemap-codec' or its corresponding type declarations.
** node-jsdom
1) Test cases only possible to test from the outside
frees up callback handles passed to setTimeout:
AssertionError: expected 15.75 to be below 5
+ expected - actual
-15.75
+5
** node-lib0
iterator.js(15,29): error TS8024: JSDoc '@param' tag has name 'f', but
there is no parameter with that name.
* Other (different errors with new and old node-typescript)
** node-config
Configuration for module developers
✗ The setModuleDefaults() method is available
» An unexpected error was caught: TypeError: Cannot set
property offset of [object Object] which has only a getter
* Innocent (same error with old and new node-typescript)
** ipywidgets
ModuleNotFoundError: No module named 'ipython_genutils'
** jupyter-notebook
ERROR in ./node_modules/postcss/lib/map-generator.js
Module not found: Error: Can't resolve './../../../buffer' in
'/<>/node_modules/postcss/lib'
** node-base64url
ERROR: Coverage for lines (97.22%) does not meet global threshold
(100%)
ERROR: Coverage for branches (75%) does not meet global threshold
(100%)
ERROR: Coverage for statements (94.73%) does not meet global
threshold (100%)
** node-configurable-http-proxy
CLI Tests custom-header
Message:
Error: Timeout - Async function did not complete within 1ms
(set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
Stack:
at
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
Message:
Error: Timeout - Async function did not complete within 1ms
(set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
Stack:
at
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
** node-fetcha
Package removed from Debian
** node-https-proxy-agent
1) HttpsProxyAgent
"http" module
should receive the 407 authorization code on the
`http.ClientResponse`:
Uncaught Error [ERR_SOCKET_CLOSED]: Socket is closed
** node-ignore
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 (87.65%) does not meet global threshold
(100%)
ERROR: Coverage for statements (92.08%) does not meet global threshold
(100%)
** node-immutable
Error
at Function.missingTransform
(/usr/share/nodejs/buble/dist/buble.cjs.js:367:9)
at Node.initialise
(/usr/share/nodejs/buble/dist/buble.cjs.js:2650:17)
at Node.initialise
(/usr/share/nodejs/buble/dist/buble.cjs.js:105:11)
at /usr/share/nodejs/buble/dist/buble.cjs.js:103:40
at Array.forEach ()
at Node.initialise
(/usr/share/nodejs/buble/dist/buble.cjs.js:103:11)
at Node.initialise
(/usr/share/nodejs/buble/dist/buble.cjs.js:105:11)
at Node.initialise
(/usr/share/nodejs/buble/dist/buble.cjs.js:2118:9)
at /usr/share/nodejs/buble/dist/buble.cjs.js:795:34
** node-inquirer
TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type
string or an instance of Buffer, TypedArray, or DataView. Received
undefined
at Object.writeFileSync (fs.js:1521:5)
at /<>/rxjs/tools/rollup-bundle.js:45:8
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:95:5)
{
code: 'ERR_INVALID_ARG_TYPE'
}
** node-parse-json
test/test.ts(1,53): error TS2307: Cannot find module 'assert' or its
corresponding type declarations.
** node-postcss-loader
src/node.ts(48,38): error TS2345: Argument of type 'string' is not
assignable to parameter of type 'BufferEncoding | undefined'.
src/volume.ts(425,51): error TS2345: Argument of type 'string' is not
assignable to parameter of type 'BufferEncoding | undefined'.
src/volume.ts(426,73): error TS2345: Argument of type 'string' is not
assignable to
Re: [Pkg-javascript-devel] Updating node-typescript to 4.6.3
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 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Updating node-typescript to 4.6.3
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 to notify and discuss. 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
[Pkg-javascript-devel] Bug#1005287: Bug#1005287: node-csstype: Build drops "; " in typescript declarations
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 indes.d.ts and index.js.flow. The result is unusable with > > tsc: > > > > /usr/share/nodejs/csstype/index.d.ts:18305:8 - error TS1005: ';' > > expected. > > > > All final ";" are dropped. > > Removing override_dh_auto_build fixes the problem (using upstream > index.d.ts and index.js.flow which are readable) > > @Julien, could you take a look ? I think the problem is that in index.d.ts we have: export type SvgAttributes = export type Globals = while upstream has: export type SvgAttributes = export type Globals = so the missing ';' is a red herring: we don't get the SvgAttributes like we should, and that's the real problem. I see that debian/nodejs/extlinks does have mdn-browser-compat-data, but it creates node_modules/@mdn/browser-compat-data -- I don't know why it does that, but it's what's breaking things as far a I can tell. Do you know how to fix it? 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
Re: [Pkg-javascript-devel] Bug#1003944: lumino: FTBFS with webpack 5: Module not found: Error: Recursion in resolving
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 needed for local build is webpack and node-webpack-source from > experimental. > During a test rebuild, lumino was found to fail to build in that situation. > I packaged latest upstream ; the package builds fine with the current webpack, I need to disable the automatic require test (how to do that isn't clear yet), but at least it builds. Apparently, building the example is what fails with webpack5, but the error message is... well, it doesn't really say what happens. Does it still fail with the new version? 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
Re: [Pkg-javascript-devel] RFS: lumino
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. > > I would like you to confirm if it's safe for sponsorship and > uploading > https://salsa.debian.org/calebpitan/lumino > > Thank you! I was about to update to latest upstream, but since there's a pending RC bug to fix, I'll wait until it's done. I'll try to review your work -- please poke me if I forget about it. Perhaps you can turn your repo into a pull request for the official package repo? 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
Re: [Pkg-javascript-devel] Unmaintained and useless packages
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000739: Missing parts of upstream
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. I think > we should revert your change and you should patch your package to use > @mdn/browser-compat-data/data.json#global_attribute instead of > mdn-browser-compat-data/html/global_attributes.json Why are you claiming this module isn't packaged... in a bug report about its packaging? Its debian/install file didn't list much, so I completed it, and it gave the other package I worked on what it wanted, just like it wanted, no patch necessary -- so I fail to see what's wrong here. I just had a look, and uscan says there's a new 4.1.2 version out, where I see html/global_attributes.json is still there. Are we looking at the same thing? I have: $ git remote -v origin https://salsa.debian.org/js-team/node-mdn-browser-compat-data (fetch) origin https://salsa.debian.org/js-team/node-mdn-browser-compat-data (push) 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
[Pkg-javascript-devel] It looks like node-rollup-plugin-typescript and ts-node have issues
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 be to blame. For node-rollup-plugin-typescript, the build itself is broken: + rollup -c src/index.js → dist/rollup-plugin-typescript.cjs.js, dist/rollup- plugin-typescript.es.js... (!) Entry module "src/index.js" is implicitly using "default" export mode, which means for CommonJS output that its default export is assigned to "module.exports". For many tools, such CommonJS output will not be interchangeable with the original ES module. If this is intended, explicitly set "output.exports" to either "auto" or "default", otherwise you might want to consider changing the signature of "src/index.js" to use named exports only. https://rollupjs.org/guide/en/#outputexports src/index.js created dist/rollup-plugin-typescript.cjs.js, dist/rollup-plugin- typescript.es.js in 46ms # Step 1: build a temporary @rollup/plugin-typescript cd packages/typescript && \ ln -s ../../../node_modules/@types/resolve node_modules/ && \ mkdir dist && \ NODE_PATH=node_modules tsc --module CommonJS --esModuleInterop src/index.ts src/watchProgram.ts:43:5 - error TS2322: Type 'Promise' is not assignable to type 'Promise'. Type 'unknown' is not assignable to type 'boolean | void'. Type 'unknown' is not assignable to type 'void'. 43 promise = Promise.race>([ ~~~ src/watchProgram.ts:43:46 - error TS2345: Argument of type 'Promise[]' is not assignable to parameter of type 'Iterable | PromiseLike>>'. The types returned by '[Symbol.iterator]().next(...)' are incompatible between these types. Type 'IteratorResult, any>' is not assignable to type 'IteratorResult | PromiseLike>, any>'. Type 'IteratorYieldResult>' is not assignable to type 'IteratorResult | PromiseLike>, any>'. Type 'IteratorYieldResult>' is not assignable to type 'IteratorYieldResult | PromiseLike>>'. Type 'Promise' is not assignable to type 'Promise | PromiseLike>'. Type 'Promise' is not assignable to type 'Promise'. Type 'unknown' is not assignable to type 'boolean'. 43 promise = Promise.race>([ ~ 44 new Promise((r) => setTimeout(r, timeout, true)), ~~~ 45 new Promise((r) => (resolve = r)) ~~~ 46 ]); ~ Found 2 errors. make[1]: *** [debian/rules:25: override_dh_auto_build] Error 2 and for ts-node, it is autopkgtest: # Searching module in /usr/lib/nodejs/ts-node # Searching module in /usr/lib/*/nodejs/ts-node # Searching module in /usr/share/nodejs/ts-node # Found /usr/share/nodejs/ts-node # Searching files to link in /usr/share/nodejs/ts-node './dist' -> '/usr/share/nodejs/ts-node/dist' './dist-raw' -> '/usr/share/nodejs/ts-node/dist-raw' './esm' -> '/usr/share/nodejs/ts-node/esm' './esm.mjs' -> '/usr/share/nodejs/ts-node/esm.mjs' './package.json' -> '/usr/share/nodejs/ts-node/package.json' './register' -> '/usr/share/nodejs/ts-node/register' # Launch debian/tests/pkg-js/test with sh -ex + test ! -e node_modules/util.promisify + mkdir -p tests/node_modules/.bin node_modules + test -L dist + rm -f dist + cp -r /usr/share/nodejs/ts-node/dist . + ln -s ../../../dist/bin.js tests/node_modules/.bin/ts-node ln: failed to create symbolic link 'tests/node_modules/.bin/ts-node': File exists autopkgtest [07:48:41]: test pkg-js-autopkgtest: -- -] autopkgtest [07:48:41]: test pkg-js-autopkgtest: - - - - - - - - - - results - - - - - - - - - - pkg-js-autopkgtest FAIL non-zero exit status 1 I write to the ml instead of opening direct bug reports because the build logs of both these packages are clean, they migrated to testing successfully, so both instances might be a change (hopefully 'a change' and not 'changes'...) somewhere else triggering issues down the line, so more information is needed to find out where exactly things are broken. 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
Re: [Pkg-javascript-devel] On node-svgo
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] On node-svgo
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 current situation is of the type I hate about javascript. We have a packaged svgo on salsa which on the plus side would give us /usr/bin/svgo work today (well, going in NEW at least). On the minus side it is obsolete and it does embed obsolete things. For a newer and more proper svgo, "npm2deb depends -r" shows we would need: - to update commander (no idea how hard that is) ; - picocolors to clear NEW ; - new packages for @trysound/sax, csso, stable and perhaps some of the b-deps (pixelmatch? playwright? pngjs?) ; In turn, stable, @trysound/sax and stable agree they want standard, so that makes it look like a good target. But standard says it wants the world. And in this big list, it seemed pkg-conf was an easy target without creepy "None" in the right column. Hélas! It wants newer versions of both its deps, find-up and load-json- file. So I tried my hand at load-json-file. Good news: it's just files to put in place, no more deps (just ava for testing). Bad news: it's now a non-require-able module, so even the auto-pkg-js-require step fails. I could make it a pure debian/install package putting the files in place, no test at all, but it would be dirty. I'm definitely open to suggestions... 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
[Pkg-javascript-devel] Bug#1001496: Unembed picocolors
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] On node-svgo
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? > > > > > > - Jonas > > > > > > ¹ Salsa is not Debian - it is a playground for creating Debian. > > > > > > > I know salsa is a playground, but I had mixed signals, so I was > > lost. > > Understood. > > I am very sorry for the way I wrote before. I took it as a fast-reply answer, and didn't take any offense :-) 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
Re: [Pkg-javascript-devel] On node-svgo
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 a good practive. We should use uscan components for > this. That package was made quite a long time ago so there was a good reason it did it like this. Indeed, thanks to you we have better tools now, but as I mentioned, I kept it at an old version (three/four years old!) because packaging a more recent one looks difficult. Shipping unupdated modules in d/node_modules is nothing when the main shipped thing is that old might not be that problematic... 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
Re: [Pkg-javascript-devel] On node-svgo
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 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 still > > say: > > > > Warnings occurred: > > [warning] csso: csso is included in node-svgo. Package it > > separately > > and remove it from node-svgo if you need it for another module. > > [warning] stable: stable is included in node-svgo. Package it > > separately and remove it from node-svgo if you need it for another > > module. > > [warning] prettier: Useless in Debian compilation, see node-jest > > for > > an example > > > > Finally, there's an ITP bug: https://bugs.debian.org/887376 -- and > > it > > doesn't look like it was ever closed. > > > > What is the status of this? > > The odd warning likely comes from here: > https://wiki.debian.org/Javascript/Nodejs/Database > > Perhaps the package simply has not yet entered Debian¹ at all? > > - Jonas > > ¹ Salsa is not Debian - it is a playground for creating Debian. > I know salsa is a playground, but I had mixed signals, so I was lost. I reworked the package a little - refraining from updating to a more recent upstream, because it looked like more work. That means quite a few patches to cope with new api in other packages, but I made autopkgtest run so I'm pretty confident about those. I'm still annoyed with: E: node-svgo source: source-is-missing debian/node_modules/csso/dist/csso-browser.js which I don't really know how I want to fix, but I think it looks pretty good. 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
[Pkg-javascript-devel] On node-svgo
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 still say: Warnings occurred: [warning] csso: csso is included in node-svgo. Package it separately and remove it from node-svgo if you need it for another module. [warning] stable: stable is included in node-svgo. Package it separately and remove it from node-svgo if you need it for another module. [warning] prettier: Useless in Debian compilation, see node-jest for an example Finally, there's an ITP bug: https://bugs.debian.org/887376 -- and it doesn't look like it was ever closed. What is the status of this? 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
[Pkg-javascript-devel] Strange hash sum mismatch with node-recast
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 amd64 node-recast all 0.20.5-2 [64.6 kB] Err:1 http://ftp.fr.debian.org/debian unstable/main amd64 node-recast all 0.20.5-2 Hash Sum mismatch Hashes of expected file: - SHA256:d1feaca7dc59f70c5124e9427d48f51f7e419669bbfd79b45a04d5d031b6199c - MD5Sum:6efa5d8eab9353529c5b9557bb523484 [weak] - Filesize:64608 [weak] - SHA512:7ee2591f1134fdebe7c93e953a6df6a8e5b9bf79b2f49c6dca6e72a491f856ed 6193ee3d72a7fc9d77b016f1b20e6affa41c286ca412c7e223df65fe335883b3 Hashes of received file: - SHA512:4757e0fc414a1ce027f2f91657d05cdb0901aeedd969ab2666eadb28a70134d1 19b5ee81f8f217efd6dbc4a28f61b6234239113351d0cb57e749dc8f11be24a1 - SHA256:d1feaca7dc59f70c5124e9427d48f51f7e419669bbfd79b45a04d5d031b6199c - MD5Sum:6efa5d8eab9353529c5b9557bb523484 [weak] - Filesize:64608 [weak] Last modification reported: Tue, 28 Sep 2021 17:28:04 + Fetched 64.6 kB in 0s (0 B/s) W: Sources disagree on hashes for supposely identical version '0.20.5- 2' of 'node-recast:amd64'. E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/n/node-recast/node-recast_0.20.5-2_all.deb Hash Sum mismatch Hashes of expected file: - SHA256:d1feaca7dc59f70c5124e9427d48f51f7e419669bbfd79b45a04d5d031b6199c - MD5Sum:6efa5d8eab9353529c5b9557bb523484 [weak] - Filesize:64608 [weak] - SHA512:7ee2591f1134fdebe7c93e953a6df6a8e5b9bf79b2f49c6dca6e72a491f856ed 6193ee3d72a7fc9d77b016f1b20e6affa41c286ca412c7e223df65fe335883b3 Hashes of received file: - SHA512:4757e0fc414a1ce027f2f91657d05cdb0901aeedd969ab2666eadb28a70134d1 19b5ee81f8f217efd6dbc4a28f61b6234239113351d0cb57e749dc8f11be24a1 - SHA256:d1feaca7dc59f70c5124e9427d48f51f7e419669bbfd79b45a04d5d031b6199c - MD5Sum:6efa5d8eab9353529c5b9557bb523484 [weak] - Filesize:64608 [weak] Last modification reported: Tue, 28 Sep 2021 17:28:04 + E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Can anybody enlighten me on what's wrong? J.Puydt PS: of course, I haven't uploaded the new node-ast-types since I can't give it the test run I wanted... -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000722: Bug#1000722: Bug#1000722: Bug#1000722: Bug#1000722: Please ship TypeScript definitions
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 magic version to look for. > > > This command, however: > > apt-cache search node-types-lodash.escape > > tells you which binary package either is or virtually provides the > package "node-types-lodash.escape". > Ah, but I knew which package I wanted already -- I just needed to see if the right experimental version was available, so apt-cache show was the right thing. 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
[Pkg-javascript-devel] Bug#1000722: Bug#1000722: Bug#1000722: Bug#1000722: Please ship TypeScript definitions
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.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 > > Not sure, but seems the above command is unreliable, and this one > works: > > apt-cache search node-types-lodash.escape > No, it's reliable, but I think I was using a mirror and it took time to get in sync. Now I could install the new package, and it looks like it would do the trick. 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
[Pkg-javascript-devel] Bug#1000722: Bug#1000722: Bug#1000722: Please ship TypeScript definitions
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 try when I see it. For the sake of completeness: that will be useful for the rendermime package of jupyterlab (but even then I'll have to clear the apputils and codemirror packages). 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
[Pkg-javascript-devel] Bug#1000739: Missing parts of upstream
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000725: Please ship TypeScript definitions
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000723: Please ship TypeScript definitions
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000722: Please ship TypeScript definitions
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000712: Please add TypeScript definitions
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000672: Bug#1000672: @lumino/polling isn't compiled correctly
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 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000672: @lumino/polling isn't compiled correctly
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 since these errors don't get caught somehow, the package still build, but with a mostly useless @lumino/polling. I had a look but didn't find inspiration. Can someone from the team get a look and tell me what's wrong? 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
[Pkg-javascript-devel] Bug#1000670: Please ship TypeScript definitions
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1000668: Please ship TypeScript definitions
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Obsolete-new packages
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, and lintian to throw warnings/errors about the "dirty > > work" > > (as opposed to notes which are quite invisible). > > I have to side with Andrius here: more and more of the JS package fall out of my reach -- notably some of the node-rollup-plugin-* packages. I'm having a though time with packages with subpackages with out-of- this-world version numbers... > > I am aware that npm2deb is not developed by Debian JS Team, thus it > > is > > quite natural it does not follow JS Team policies close enough. > > Maybe it > > should be taken over by Debian, or its usage to do packaging in > > Debian > > be strongly discouraged? (Maybe it is already, only I am not > > aware). > > I just updated npm2deb, however it is a good practice to launch > `lintian-brush`. In addition, npm2deb's agorithm is very > questionable, in particular for the search for reverse dependencies. > I didn't know about lintian-brush. I'll give it a test drive. > I'll try to package my personal tools which permits to fix many > things automatically. The best would to include them in lintian-brush > but sadly I've no talent in Python (all my tools are Perl scripts). For my packages I don't have personal tools, only a personal routine: (1) "lintian -I" to get things right (sometimes adding a --pedantic when I'm feeling in the mood) ; (2) build the source package in a schroot-sbuild-unstable to check I got deps right after the initial round of ; (3) if it's a sensitive package (fragile and important rdeps I know about), I put the binary packages in my local repo, and try to build a random few of the reverse-deps by hand with them ; (4) upload. This isn't perfect: I uploaded a newer node-typescript a few weeks ago and it broke ts-node (which obviously wasn't in the list of rdeps I had checked). I can't update it to a newer upstream which would fix the issue because it has new deps (or deps with newer versions), so I'm mostly waiting for those to clear before I can finally fix it. 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
[Pkg-javascript-devel] Bug#1000203: Please add @yarnpkg/fslib to the package
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#999460: Bug#999460: Please package TypeScript definitions @types/emscripten
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 relationship? > > Alternatively, vould you please test if simply adding newest release > works for your usecase - as a relatively simple minimal test? > I'm interested in it because I would like to update ts-node, which now wants @yarnpkg/fslib, which wants @types/emscripten, so I don't have much details and my use-case is inexistant for the moment. I tried to have a look around, but didn't find any conclusive information. The last @types/emscripten release if four months old, so they must be a little behind. 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
[Pkg-javascript-devel] Bug#999460: Please package TypeScript definitions @types/emscripten
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 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Bad filenamemangle in many of our packages
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#984607: RGI_Emoji will come
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994545: Upstream bug
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 fixed lumino to experimental too. 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
[Pkg-javascript-devel] Bug#994545: Working on the problem
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Export both ESM and CommonJS modules
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 edges rather than the center). > > (4) postpone upload of A until no other Node.js experiment is > ongoing. I'll try to do better next time. Sorry for the inconvenience, 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
Re: [Pkg-javascript-devel] Export both ESM and CommonJS modules
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. Well, I still felt blamed, and it's only partly justified. In that particular case, I saw the problem, produced a -1 with a patch to avoid breaking deps, but asked around because it was somehow not satisfying, with mostly two questions: 1. if what I did was a good idea? 2. how to do something clean? The summary of the answers is that it was a bad idea (don't diverge from upstream unless you're ready to take matters on your shoulders), but there was no clean solution. I hence broke things with -2: that's just the first occurrence of an emerging matter, so waiting won't make it go away. Bite the bullet rather sooner than later, one may say. Let's imagine a simple situation where we have three packages A, B and C with B and C depending on A using 'require', then upstream A decides it's now import and not require, B follows suit and C trails behind ; there are mostly two solutions: (1) do dirty things with A's packaging, so it allows both require and import, with the three defects that: (i) the require part is on our shoulders; (ii) someone using A packaged by Debian might not realize their code is subtly wrong ; (iii) the C package looks like its nice and clean... even though it's the reason why A's is dirty and we have problems (i) and (ii)! (2) let A and B go forward, and make C's package dirty -- as it deserves. > So now I will avoid fixing bugs other than what I generated. I'm sorry if I offended you: you've always been very helpful, and much more competent than me when it comes to JS (your solution here is an example). 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
Re: [Pkg-javascript-devel] Export both ESM and CommonJS modules
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 > node-strip-json-comments which broke eslint) > You'll notice that before uploading the breaking node-strip-json-comments, I did write to this list to ask for advice, and uploaded a -1 which could still be required (but not imported, breaking upstream in a way). And the sound advice was: follow upstream. So I uploaded -2 which broke requiring deps; but could be imported like upstream meant. It we had something automatically doing the require-and-import trick, that could be a temporary solution. Very very temporary. But this workaround is manual and goes in the wrong direction, so I'm voting against it. It looks like it could silently build up a technical debt... until shit hits the fan (a when, not an if), then we'll have to foot the bill. 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
[Pkg-javascript-devel] Issues with node-rollup-plugin-node-resolve
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 or +ds or +repack suffix... - I still have a failing test in the upstream test suite (heavily patched to use tape instead of ava... will have to check for a RFP), with little clue as to why it is failing. If you have insight or ideas about those matters, don't hesitate: I won't touch the package in the coming days... 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
[Pkg-javascript-devel] Bug#993693: ReferenceError: options is not defined
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 Object.apply (/usr/share/nodejs/webpack/lib/config/defaults.js:873:30) at WebpackOptionsApply.process (/usr/share/nodejs/webpack/lib/WebpackOptionsApply.js:453:16) at createCompiler (/usr/share/nodejs/webpack/lib/webpack.js:78:28) at create (/usr/share/nodejs/webpack/lib/webpack.js:115:15) at webpack (/usr/share/nodejs/webpack/lib/webpack.js:123:46) at f (/usr/share/nodejs/webpack/lib/index.js:35:15) at WebpackCLI.createCompiler (/usr/share/nodejs/webpack- cli/lib/webpack-cli.js:176:24) at WebpackCLI.run (/usr/share/nodejs/webpack-cli/lib/webpack- cli.js:268:25) at async runCLI (/usr/share/nodejs/webpack- cli/lib/bootstrap.js:59:9) This means it's broken ; installing unstable's 4.43.0-6 made the error go away, so it's a problem only with the new version. 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
[Pkg-javascript-devel] Bug#993167: dont_be_a_module.patch is too dirty
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] node-strip-json-comments: a dirty patch
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 strip-json-comments declares it's a JS- module -- hence it can't be require'd. With my dirty patch, I made it possible again, so existing node-* packages work -- that was the goal: don't break deps. But of course, future packages (or future versions of existing ones) will probably work différently. Let's assume in the near future we end up with: (1) node-foo wants to import node-strip-json-comments ; (2) node-bar wants to require it. If I understand well, without my dirty patch, node-bar has a problem, and with it node-foo has a problem. So my question is: is it possible to handle things cleanly and how? [If not, I'll drop the patch and upload a breaking package immediately: the sooner broken, the sooner fixed...] 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
[Pkg-javascript-devel] node-strip-json-comments: a dirty patch
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 require'd. Yes, that meant autopkgtest-pkg-nodejs' most basic test was failing! And I figured that also meant every dep in Debian would fail likewise. So the new patch: https://salsa.debian.org/js-team/node-strip-json-comments/-/blob/master/debian/patches/dont_be_a_module.patch reverts upstream's change, so hopefully everything keeps on working. But still, I find it dirty, and when we'll have both deps which require and deps which import, we'll probably have a problem. Can someone more knowledgeable chime in and make nice observations/propositions? 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
[Pkg-javascript-devel] Bug#976657: Please ship TypeScript descriptions
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#974648: Also for pretty-format and jest-diff
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 'jest-diff' modules. 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
[Pkg-javascript-devel] Bug#974842: Please package newer upstream versions
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
[Pkg-javascript-devel] Bug#974648: Please really ship TypeScript definitions
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#974201: Now blocking
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#904723: Why is the last version of node-diff not in unstable?
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 step on your toes. 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
[Pkg-javascript-devel] Bug#974425: The salsa git repository isn't up to date
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 tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b " suffix to indicate what branch is used for the Debian packaging. 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
[Pkg-javascript-devel] Bug#974202: Please ship TypeScript definitions
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: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/diff Here is how I did the change in another team-maintained package: https://salsa.debian.org/js-team/node-source-map-support/-/commit/8f25b98575e083aa7b243e8d92e365751e3ae8cd (I might do it myself at some point when it becomes the top item on my TODO-list) 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
[Pkg-javascript-devel] Bug#974201: Please ship TypeScript definitions
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 like to package on my way to JupyterLab. Here is how I did the change in another team-maintained package: https://salsa.debian.org/js-team/node-source-map-support/-/commit/8f25b98575e083aa7b243e8d92e365751e3ae8cd 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
Re: [Pkg-javascript-devel] Bug#974082: Please ship TypeScript definitions
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
Re: [Pkg-javascript-devel] doubt with autopkgtest for javascript packages
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: node-ast-types node-es5-shim node-esprima-fb node-mocha-lcov-reporter node-posix-getopt node-regenerate node-stringmap node-unicode-canonical-property-names-ecmascript node-unicode-property-aliases-ecmascript node-unicode-property-value-aliases 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
[Pkg-javascript-devel] Bug#974082: Bug#974082: Please ship TypeScript definitions
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#974082: Bug#974082: Please ship TypeScript definitions
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 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#974082: Please ship TypeScript definitions
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#974072: Please ship typescript definitions
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: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/json5 and jupyterlab, which I'm trying to package, already makes use of those... 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
[Pkg-javascript-devel] Bug#974030: Add the main component to Provides if it doesn't match the package name
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
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#973983: Bug#973983: pkg-js-tools tries to require a non-existing name
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 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 chosen one's directory! > > > > That's definitely not correct. > > $ echo '*' > debian/nodejs/root_modules The package builds, with just: W: node-lumino: nodejs-module-not-declared node-lumino-datastore usr/share/nodejs/@lumino/datastore/package.json The inspection of the output of dpkg-deb -c doesn't show anything surprising. Running through autopkgtest works. I'm uploading the result ; the repo is now here: Vcs-Git: https://salsa.debian.org/js-team/lumino.git Vcs-Browser: https://salsa.debian.org/js-team/lumino 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
[Pkg-javascript-devel] Bug#973983: Bug#973983: pkg-js-tools tries to require a non-existing name
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 chosen one's directory! That's definitely not correct. 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
[Pkg-javascript-devel] Bug#973983: Bug#973983: pkg-js-tools tries to require a non-existing name
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
> > structure:
> > - no main module ;
> > - only packages.
>
> Hi,
>
> did you try to set onne of them in debian/nodejs/main ?
Uh... no, I hadn't, since there's no main. Now I have tried setting one
as such and it goes through.
> > My d/control has a build dep on pkg-js-tools, and uses "Provides:
> > ${nodejs:Provides}" ; I have a d/nodejs/additional_components with
> > packages/* to find the packages and my d/tests/pkg-js/test is only
> > an
> > "echo FIXME".
> >
> > When building the package, I get strange warnings, but they seem
> > pretty
> > harmless :
> >
> > dh_auto_install: warning: # /! "types" field should be replaced by
> > "typings" in packages/algorithm/package.json
> > Please report this bug
>
> @praveen asked for this warning
I tried to search the web about it, and found only:
https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html
I don't care either way.
> > indeed, the main package.json has no 'name' field. It should
> > instead try to require the packages listed in
> > d/nodejs/additional_components.
That was a bad idea : some of them only work in a browser (they use
navigator) ; I chose one who doesn't for d/nodejs/main.
I still have a lintian warning:
W: node-lumino: nodejs-module-not-declared node-lumino-datastore
usr/share/nodejs/@lumino/datagrid/package.json
which is strange since I use ${nodejs:Provides} in d/control...
The question is whether it is a problem with pkg-js-tools or with
upstream : in the first case this bug report is legit, in the second
case I should close that one and open one upstream.
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
[Pkg-javascript-devel] Bug#973983: pkg-js-tools tries to require a non-existing name
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
packages/* to find the packages and my d/tests/pkg-js/test is only an
"echo FIXME".
When building the package, I get strange warnings, but they seem pretty
harmless :
dh_auto_install: warning: # /! "types" field should be replaced by
"typings" in packages/algorithm/package.json
Please report this bug
Things get bad when autopkgtest kicks in and tries to require:
autopkgtest [15:44:43]: test pkg-js-autopkgtest-require: [-
--
Using package.json
Node module name is
Test: require
internal/modules/cjs/loader.js:898
throw new ERR_INVALID_ARG_VALUE('id', id,
^
TypeError [ERR_INVALID_ARG_VALUE]: The argument 'id' must be a non-
empty string. Received ''
at Module.require (internal/modules/cjs/loader.js:898:11)
at require (internal/modules/cjs/helpers.js:74:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:120:18)
at Object.runInThisContext (vm.js:309:38)
at Object. ([eval]-wrapper:10:26)
at Module._compile (internal/modules/cjs/loader.js:1015:30)
at evalScript (internal/process/execution.js:94:25)
at internal/main/eval_string.js:23:3 {
code: 'ERR_INVALID_ARG_VALUE'
}
indeed, the main package.json has no 'name' field. It should instead
try to require the packages listed in d/nodejs/additional_components.
Is it possible to get around it?
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
[Pkg-javascript-devel] Bug#972487: ITP: lumino -- large set of libraries to develop Node.js applications
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 to develop Node.js applications It is a dep of the next ipywidgets ; the previous version used PhosphorJS, but that project was abandoned by its upstream, so the Jupyter Project took over the maintenance under this new name. I plan to maintain it within the Debian Javascript Maintainers team. 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
[Pkg-javascript-devel] Bug#972486: Please ship typescript type definitions
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#972485: Please add typescript type declarations
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Jupyter project packaging effort
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, but there's a widgetsnbextension/ directory. "Lasciate ogni speranza, voi ch'entrate" would be a more suitable name, though longer. What is it? A trivial Python code, with a few javascript source files, which need to be "compiled" (webpack'ed, really). The package existed, so it just needs brushing, ok? Well, the short answer is: no. The longer answer is that in debian/, there is a lot of javascript code. Not even always sources. When the package was (last) prepared, Debian lacked many, many things on the javascript side, so there was little choice in the matter. The elephant in the room is webpack : but now we have it! There are still probably dozens of missing depends, all in a dep graph, probably not a tree (there will be loops). I'll probably prepare quite a few package both in the Debian Python Team and the Debian Javascript Maintainers Team. I'm sorry if I'm breaking some things along the way : I'll do my best to avoid that, but from experience you can hardly upgrade things on one side without breaking something on another... Help is welcome, 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
[Pkg-javascript-devel] Bug#968970: Please add typescript definitions to the package
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 : https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/sinonjs__fake-timers 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
[Pkg-javascript-devel] Bug#968969: Please add typescript definitions to the package
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#968968: Please add the parse5 type definitions
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 Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#968966: Please add typescript definitions
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#968962: Full list of missing deps
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 : with these the package will be unbroken. 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
[Pkg-javascript-devel] Bug#968962: Doesn't ship all deps from what it ships
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 the node-braces package doesn't contain the type declarations (their upstream doesn't ship them), so it's really the files coming from DefinitelyTyped which should get used. I decided to set the severity to important, because it looks like more than a normal bug : it's not enough to add @types/braces to fix it ; perhaps there are other instances where broken type definitions are shipped, in the sense that they should be in the package. I'll probably follow up to that initial mail with a full list of problems. 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
[Pkg-javascript-devel] Bug#968930: Please update tslib to version 2.0.1
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 https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Updating node-magic-string
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 checked).
Perhaps it's just a question of updating the tests... but I am not
convinced it's the only problem (otherwise a trivial patch will make
tests pass!), so if someone could have a look and confirm, that would
help.
Thanks,
J.Puydt
PS: the end of the failing log is :
525 passing (5s)
2 pending
2 failing
1) buble
cli
creates-inline-sourcemap:
AssertionError [ERR_ASSERTION]: [ { name: 'output.js',
contents:
'var answer = function () { return 42; };\n\n//#
sourceMappingURL=data:application/... deepEqual [ { name: 'output.js',
contents:
'var answer = function () { return 42; };\n\n//#
sourceMappingURL=data:application/...
+ expected - actual
[
{
-"contents": "var answer = function () { return 42; };\n\n//#
sourceMappingURL=data:application/json;charset=utf-
8;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoib3V0cHV0LmpzIiwic291cmNlcyI6WyIuLi
9pbnB1dC5qcyJdLCJzb3VyY2VzQ29udGVudCI6WyJjb25zdCBhbnN3ZXIgPSAoKSA9PiA0M
jtcbiJdLCJuYW1lcyI6WyJjb25zdCJdLCJtYXBwaW5ncyI6IkFBQUFBLEdBQUssQ0FBQyxN
QUFNLFlBQUcsWUFBTSxLQUFFLENBQUM7In0="
+"contents": "var answer = function () { return 42; };\n\n//#
sourceMappingURL=data:application/json;charset=utf-
8;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoib3V0cHV0LmpzIiwic291cmNlcyI6WyIuLi
9pbnB1dC5qcyJdLCJzb3VyY2VzQ29udGVudCI6WyJjb25zdCBhbnN3ZXIgPSAoKSA9PiA0M
jtcbiJdLCJuYW1lcyI6WyJjb25zdCJdLCJtYXBwaW5ncyI6IkFBQUFBLEdBQUssQ0FBQyxN
QUFNLFlBQUcsR0FBRyxTQUFHLEtBQUUsQ0FBQzsifQ=="
"name": "output.js"
}
]
at child_process.exec (test/test.js:119:15)
at ChildProcess.exithandler (child_process.js:285:7)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit
(internal/child_process.js:259:5)
2) buble
cli
creates-sourcemap:
AssertionError [ERR_ASSERTION]: [ { name: 'output.js',
contents:
'var answer = function () { return 42; };\n\n//#
sourceMappingURL=output.js.map' },... deepEqual [ { name: 'output.js',
contents:
'var answer = function () { return 42; };\n\n//#
sourceMappingURL=output.js.map' },...
+ expected - actual
}
{
"contents": {
"file": "output.js"
- "mappings": "A,GAAK,CAAC,MAAM,YAAG,YAAM,KAAE,CAAC;"
+ "mappings":
"A,GAAK,CAAC,MAAM,YAAG,GAAG,SAAG,KAAE,CAAC;"
"names": [
"const"
]
"sources": [
at child_process.exec (test/test.js:119:15)
at ChildProcess.exithandler (child_process.js:285:7)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit
(internal/child_process.js:259:5)
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] node-typescript-types should die
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 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Rollup in Debian
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 experimental ? Is there a plan to package the merged plugins ? Can I lend a hand ? Happy new year js-team! 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
[Pkg-javascript-devel] Bug#943526: Bug#943526: Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib
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, > > > > > > 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 > > When installing using `npm install typescript`, there is no > "node_modules/tslib", so there is no reason to provide such link IMO. > Would that break anything if node-typescript didn't provide the link? I don't remember why I added it, but I most certainly didn't add it just like this... 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
[Pkg-javascript-devel] Bug#943526: Bug#943526: node-tslib: directory vs. symlink conflict: /usr/share/nodejs/tslib
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 list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#942809: Bug#942809: Bug#942809: Why embed ts-node in node-typescript?
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 want more embedding for javascript packages to > reduce the number of binary packages. They don't even allow multiple > binary packages from same source package if one of the binary is > javascript/node (for example ruby-task-list). I don't think the NEW > queue situation is healthy. It is seriously demotivating and I > totally understand wanting to avoid it. Then it looks like a complaint that needs escalating, not trying to get around... 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
[Pkg-javascript-devel] Bug#942809: Bug#942809: Why embed ts-node in node-typescript?
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? > > > > I don't see the point into packaging those together... > > It was an attempt to avoid waiting 6 or 7 months in the NEW queue > with a 50% chance of getting an acceptance or never getting an answer > (which seems to be considered as a rejection, see node-mimelib for > example). Well, I know the NEW queue is kind of a pain, but there's a reason why it's there, so getting around it isn't a good solution. 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
[Pkg-javascript-devel] Bug#942809: Why embed ts-node in node-typescript?
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
Re: [Pkg-javascript-devel] Troubles with tsc
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 find global type 'CallableFunction'. > error TS2318: Cannot find global type 'Function'. > error TS2318: Cannot find global type 'IArguments'. > error TS2318: Cannot find global type 'NewableFunction'. > error TS2318: Cannot find global type 'Number'. > error TS2318: Cannot find global type 'RegExp'. > > Is there a problem with typescript-types/unstable ? > > I pushed my work to salsa > Yes, Bastien broke node-typescript yesterday... can't blame him : - I tried the same hack before (literally: I uploaded a version with the same patch, and a few hours later dropped it in a new upload) ; - those who don't do anything, don't break anything... I'm still glad he tries to lend a hand :-) 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
