unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: guix-devel <guix-devel@gnu.org>
Subject: Packaging node-mocha
Date: Tue, 27 Nov 2018 22:23:23 +0100	[thread overview]
Message-ID: <7241ff56-0f62-d8a5-e4f9-c14af37426b3@riseup.net> (raw)
In-Reply-To: <mochajs/mocha/issues/3575/441483311@github.com>

Hi people

I asked on a couple of popular packages to get a list of what devdeps 
were actually needed to build the package.

Here is an example of a response:
Out of 36 devdeps only 4 are builddeps and another 2 are testdeps.

I use answers like these to populate my blacklist which now has about 
100 blocked packages.

I won't proceede with mocha at this point as browserify is a builddep an 
is known to be complex.

-------- Forwarded Message --------
Subject: 	Re: [mochajs/mocha] Build or build+test dependencies (#3575)
Date: 	Sun, 25 Nov 2018 23:22:43 +0000 (UTC)
From: 	P. Roebuck <notifications@github.com>
Reply-To: 	mochajs/mocha 
<reply+00f948330f670a17d96971ef5994a7d733491955fe51d07792cf000000011812f0c392a169ce16dd7de8@reply.github.com>
To: 	mochajs/mocha <mocha@noreply.github.com>
CC: 	swedebugia <swedebugia@riseup.net>, Author <author@noreply.github.com>



To the best of my knowledge...


     Mocha devDependencies


       build


         browser bundling

   * "browserify"
   * "package-json-versionify"
   * "through2"
   * "watchify"


       documentation

   * "jsdoc"
   * "markdown-toc"


         website generation

   * "@mocha/docdash"
   * "assetgraph-builder"
   * "svgo"


       linting

   * "eslint"
   * "eslint-config-prettier"
   * "eslint-config-semistandard"
   * "eslint-config-standard"
   * "eslint-plugin-import"
   * "eslint-plugin-node"
   * "eslint-plugin-prettier"
   * "eslint-plugin-promise"
   * "eslint-plugin-standard"
   * "lint-staged"
   * "markdownlint-cli"
   * "prettier-eslint-cli"


       testing

   * "coffee-script"
   * "cross-spawn"


         assertion libraries

   * "chai"
   * "unexpected"


         browser testing

   * "karma": "^2.0.2",
   * "karma-browserify": "^5.0.5",
   * "karma-chrome-launcher": "^2.0.0",
   * "karma-mocha": "^1.3.0",
   * "karma-mocha-reporter": "^2.2.4",
   * "karma-sauce-launcher": "^1.2.0",


         coverage testing

   * "coveralls"
   * "nyc"


       other

   * "husky": forces |lint| and |test| checks for |git commit|
   * "nps": migrates |npm| scripts outside "package.json"
   * "rimraf": portable |rm -rf| command

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub 
<https://github.com/mochajs/mocha/issues/3575#issuecomment-441483311>, 
or mute the thread 
<https://github.com/notifications/unsubscribe-auth/APlIM1LlogEkqEemSoKGADT5k_VBCgL9ks5uyyZDgaJpZM4Yvs12>.

           reply	other threads:[~2018-11-27 21:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mochajs/mocha/issues/3575/441483311@github.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7241ff56-0f62-d8a5-e4f9-c14af37426b3@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).