Trey Hunner said [0], "Blanket and qunit are the only real requirements here. We may be able to switch away from Grunt and use those together in a more manual fashion so requirements can be upgraded easily."
[0] https://github.com/django/django/pull/4889#issuecomment-219921988 On Thursday, August 25, 2016 at 9:31:08 AM UTC-4, Josh Smeaton wrote: > > Hi All, > > While building out a vagrant image for running django's tests (plug: > https://github.com/django/django-box) I came across a problem trying to > run the javascript tests as defined by the tox.ini file. It ended up being > the same problem as raised in https://code.djangoproject.com/ticket/25803. > The fix to that ticket was to update the package.json dependencies listing > npm as < 3.0.0, but I'm wondering if there's a longer term solution we're > going to need to look at. > > https://github.com/ModelN/grunt-blanket-qunit appears to be abandoned and > is probably the main cause of us requiring npm version 2. Maybe we could > look at separate packages for generating code coverage and running qunit > tests? Does that sound right? I'm happy to open a ticket to track this, but > just wanted to see if it's needed or already on someones radar. > > Cheers > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d41a4227-9979-47b9-8260-ae45d15415ee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
