Allow setting of arbitrary process.env variables about grunt-express-server

[ericclemmons]

@C-Das I whole-heartedly agree! Although, I would like to introduce your change as a major version upgrade with one additional change (which I can take care of):

• The removal of htmlmin.

Our changes together would be a well-earned major version to this project.

Let me know what you think. Thanks!

[cdax]

Sure, sounds fantastic! This way I also get time to think about unit testing.

PS: Sorry about the late response, I was away for the weekend.

[cdax]

Hi,

I've started working on this over at https://github.com/c-das/grunt-express-server/tree/adds-env-option . I'll submit a PR to your major version branch when it's ready.

[oshybystyi]

what about DEBUG=server grunt ?

[oshybystyi]

In case you're using DEBUG=server grunt you're also need to modify ./bin/www (if you've generated project using express-generator), so it contains line debug.log = console.log.bind(console); so debug module sends messages to stdlog instead of stderr, otherwise watch task won't be started before first request to application.

[GrayedFox]

Would someone be so kind as to post a working grunt file example here, along with an edited www file (if necessary)?

I followed the express generator as well and am trying to get the config right.

Gruntfile (showing relevant bits):

  grunt.initConfig({
    watch: {
      express: {
        files: [
          'app.js',
          'bin/www',
          'public/**/*.js',
          'public/**/*.cs',
          'routes/*.js',
          'views/*.jade'
        ],
        tasks: ['express:dev'],
        atBegin: true,
        spawn: false
      }
    },

    express: {
      dev: {
        options: {
          script: './bin/www'
        }
      }
    }
  });

  grunt.loadNpmTasks('grunt-contrib-watch');
  grunt.loadNpmTasks('grunt-express-server');

  grunt.registerTask('server', ['watch:express']);

Grunt correctly finds the www file and starts it however, for some strange reason, none of the CSS / styling appears when loading a page, and as soon as I hit the server it crashes (so any subsequent calls fail, since the server has stopped after the initial one).

This same behaviour occurred even if I add the debug server env variable, like so:

    env: {
      DEBUG: 'server'
    }

Any help really appreciated - also happy to make a commit to clean up the read me and make turn this Q&A into a guide on the landing repo page 👍 😄

[mdrmuhaimin]

@ericclemmons @cdax ericclemmons Any update on this issue or timetable when this feature will get released?