Debian Browserify

198 Members
Mentoring Newbies in node/js packaging | Originally: package nodejs tools like browserify/webpack/rolup/babel. browserification is the process of adapting code written for nodejs to run on a browser. This may include combining modules to a single file or adding functionality only present in nodejs | Pre requisites  https://wiki.debian.org/Packaging/Pre-Requisites (Gives you instructions to setup a development environment)37 Servers

Load older messages

Timestamp Message
23 Jan 2020

gargantua_kerr: and most important is never remove something you are not sure about

Right. Will switch them back,
Also is there a tool to generate the same? The earlier scirpt is a complete Makefile

04:48:02@gargantua_kerr:matrix.orggargantua_kerrIn terms of build variables
04:58:39@praveen:poddery.comPirate ‍ Praveengargantua_kerr: did you check if it build depends on cdbs ?
04:59:00@praveen:poddery.comPirate ‍ PraveenWhich is completely different from debhelper
04:59:41@praveen:poddery.comPirate ‍ PraveenYou will have to learn how to use cdbs for packaging first

You will have to learn how to use cdbs for packaging first

Alrighty. This is interesting. Would you have a documentation for it?


This doesn't seem to exist, anymore.

05:07:28@praveen:poddery.comPirate ‍ Praveengargantua_kerr: check in cdbs package itself
24 Jan 2020

Pirate ‍ Praveen: Noted, and reading.
Meanwhile I figured the issue with node-uniq.
Node.js 12 uses Tim sort so the comparison order changes. And the expression used in node-uniq will return the result in reverse order than expected.


This further explains it. I feel that the test isn't robust enough, like it is mentioned in the thread.
Do you think we can change the test accordingly, or should the test be dropped altogether instead?

16:42:05@gargantua_kerr:matrix.orggargantua_kerrAlso opened an issue to request for the same, but it seems unmaintained,
18:52:26@praveen:poddery.comPirate ‍ Praveengargantua_kerr: we can disable now
20:32:33@praveen:poddery.comPirate ‍ Praveen gargantua_kerr: I think yadd fixed it now, it'd be a good idea to add your name in the wiki when taking a package
20:37:53@_oftc_yadd:matrix.orgyadd Pirate ‍ Praveen: Hi, there is a bug in node-lodash that makes node-grunt-legacy-util build fails
20:38:03@gargantua_kerr:matrix.orggargantua_kerr Pirate ‍ Praveen: yep. I updated the wiki with a PR I made. He pulled in my PR, fixed and uploaded. He's fast!
20:39:07@praveen:poddery.comPirate ‍ Praveengargantua_kerr: good!
20:39:20@gargantua_kerr:matrix.orggargantua_kerr yadd: yeah, runInContext() doesn't seem to work.
20:39:35@praveen:poddery.comPirate ‍ Praveen yadd: I'm traveling, see if you can find a way
20:40:40@praveen:poddery.comPirate ‍ PraveenSome steps we miss in lodash build?

yadd: yeah, runInContext() doesn't seem to work.

Also found a fix for the earlier error with grunt-legacy-util.
Just doing NODE_NO_WARNINGS=1 fixes the error.
Tried that with upstream repo,

20:52:59@praveen:poddery.comPirate ‍ Praveengargantua_kerr: I think that is hiding or work around, not a fix
20:54:47@gargantua_kerr:matrix.orggargantua_kerr Pirate ‍ Praveen: The tests were taking stdout for comparing the values.
While the stdout results were OK, there are several deprecation warnings about Buffer() from upstream itself.
So the warnings too were concatenated in the variables making the tests fail.
20:58:28@gargantua_kerr:matrix.orggargantua_kerrThe warnings are not an issue with upstream results, so I was guessing maybe this is a fix.
20:58:52@gargantua_kerr:matrix.orggargantua_kerr I'll check in if something else can be a better way
21:11:14@praveen:poddery.comPirate ‍ Praveengargantua_kerr: the fix is to not have the warnings in the first place
21:12:09@praveen:poddery.comPirate ‍ Praveenie, change the usage as suggested in the warnings
21:14:27@gargantua_kerr:matrix.orggargantua_kerrRedacted or Malformed Event
21:16:18@gargantua_kerr:matrix.orggargantua_kerr Pirate ‍ Praveen: Right.
They are however warnings from upstream code itself. I'll try fixing them, then.
I have opened an issue upstream too,
21:56:04@gargantua_kerr:matrix.orggargantua_kerrFixed the warnings, tests pass. Made a PR upsteam, all checks pass. That should, hopefully fix the error as the lodash thing is resolved.
25 Jan 2020
06:57:03@praveen:poddery.comPirate ‍ Praveengargantua_kerr: 👍

There are no newer messages yet.

Back to Room List