Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Watch/launch errors when I grunt run #13

BigAB opened this Issue · 9 comments

3 participants


Windows 7

Running "watch" task
Waiting...>> undefined: [Lundefined:Cundefined] watch EPERM
Error compiling LESS. Use --force to continue.
info: Web server started at http://localhost:9101
info (launcher): Starting browser "PhantomJS"
info (watcher): Watching "C:/Lineman/node_modules/testacular/adapter/jasmine.js"
info (watcher): Watching "C:/Lineman/node_modules/testacular/adapter/lib/jasmine.js"
info (watcher): Watching "C:/Lineman/generated/js/spec.js"
info (watcher): Watching "C:/Lineman/generated/js/app.js"
error (launcher): Error: Command failed: 'undefined' is not recognized as an internal or external command,
operable program or batch file.


Hey Adam, are you using the default configuration of Lineman or do you have additional .less files that are getting compiled? If you have customizations can you post a gist of what your less files for the project look like? I believe the last line:


comes from an issue where Testacular is not able to find the PhantomJS installation in Windows. I actually worked on this earlier this week as I built up a dev env in Windows 7 to see how things would work. I have an open ticket to replace Testacular with Testem, another library that can run headless specs that works much better on Windows.



Just the files included after running:

lineman Lineman
cd Lineman
grunt run

...(or grunt.cmd run), and straight up grunt get's similar errors.

Also running:

phantomjs so not sure what the issue is.


Hey Adam, I just pushed a new version which replaces our spec runner dependency Testacular with the much more capable Testem. This update adds 2 new commands to the CLI for lineman: lineman run and lineman spec. The intent is to get the app running and watching files with run and then fire up spec in another terminal tab.

While this update doesn't touch LESS compilation, could you update from npm and try out the new workflow and see if you still encounter these issues?


Just wanted to ping you @BigAB and see if you had time to pull a new version of Lineman and test this again?


Not as of yet. Will try to do it and report back as soon as I can. May not be today though.


So... todays things.
Updated lineman from NPM.

As per readme I tried lineman new Lineman
and it created a project called new

I sigh and cd new
and as per readme try `lineman spec'
and it makes a new project in spec directory

I sigh and go to delete it but it turns out the operating system can't delete all files because the filenames (paths) are too long!


So I Google, get that all cleaned up and try again:
lineman Lineman this time to not get a project called new
I notice the commands say grunt run so I do that and hey, works a little better this time, minus the less problem that still there:

Running "watch" task
Waiting...>> undefined: [Lundefined:Cundefined] watch EPERM
<WARN> Error compiling LESS. Use --force to continue. </WARN> 

I try grunt spec

Running "configure" task

Running "spec" task

    throw err;
Error: Cannot find module 'C:\Lineman\node_modules\testem\testem.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.runMain (module.js:492:10)
    at process.startup.processNextTick.process._tickCallback (node.js:244:9)
<WARN> Spec execution failed with exit code 1 Use --force to continue. </WARN>

Aborted due to warnings.

So apparently I am missing testem. npm install testem
I try grunt spec again

Open the URL below in a runner to connect.
Open the URL below in a runner to connect.
  Chrome 22.0 |
    0/0 x     |
Uncaught ReferenceError: module is not defined at http://localhost:7357/grunt.js, line 2 

So, yeah... not sure what's up there.

I try grunt
This seems to go well.

I try grunt clean
This seems to go well as well.

If I could solve the watch error, the un-deletable node-modules directory, and running the specs I might try using this.

probably need to change the readme too, it seems very out of date.


Phew! Looks like I need to revisit my windows testing to see what the heck went wrong. Thanks for your detailed testing breakdown @BigAB, I'll spend some time in the next couple of days to take a look.

Any suggestions or pull requests that would update the documentation to be more clear would be greatly accepted :)


Closing as I tested the most recent release against Windows 7.

@davemo davemo closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.