Good question, lol.. that might be even better, and fix the issue I was talking about. Perhaps even a GitHub commit URL if that is possible. There is also something like jasmine-node that could work (which was not awesome when we first started using node + jasmine). Perhaps I'll see about one of those vs directly adding it to the tree, then. :-)
On Thu, Apr 11, 2013 at 10:12 AM, Filip Maj <[email protected]> wrote: > Yea axe that stuff > > Why can't this be added as a devDependency to package.json ? > > On 4/11/13 4:00 PM, "Gord Tanner" <[email protected]> wrote: > > >+1 > > > >submodules have always annoyed me. Cleaning up our installation / dev env > >setup would be nice and tie in good with attempting to get `npm install` > >support working > > > > > >On Wed, Apr 3, 2013 at 4:06 PM, Dan Silivestru > ><[email protected]>wrote: > > > >> +1 > >> > >> I think we've talked about doing this for a little while. > >> > >> > >> > >> On Wed, Apr 3, 2013 at 3:55 PM, Brent Lintner <[email protected] > >> >wrote: > >> > >> > Hey all, > >> > > >> > I want to remove our Jasmine dependency from .gitmodules because it is > >> the > >> > only thing used as a .git module, and because git submodules have (in > >>my > >> > experience) been more annoying to have than the benefit they provide. > >> > Instead, it will be added directly to the project source tree (like > >> > everything else that is not in the NPM registry). > >> > > >> > This will also remove all use of .gitmodules, and will also remove a > >> single > >> > step in 'configure', leaving only npm calls, which will make > >>installation > >> > more simple and straightforward. > >> > > >> > I will also be removing and re-adding the latest version of Jasmine. > >> > > >> > Thoughts? > >> > > >> > -- > >> > Brent > >> > > >> > >> > >> > >> -- > >> Dan Silivestru > >> +1 (519) 589-3624 > >> > > -- Brent
