Closed victorwpbastos closed 10 years ago
Hmmm interesting plugin. I haven't used them in conjunction yet. Any luck on your side?
I'm not using Grunt anymore. Em 22/07/2014 00:16, "Drewz" notifications@github.com escreveu:
Hmmm interesting plugin. I haven't used them in conjunction yet. Any luck on your side?
— Reply to this email directly or view it on GitHub https://github.com/drewzboto/grunt-connect-proxy/issues/56#issuecomment-49693711 .
@victorwpbastos if you do decide to go back to Grunt and use jit-grunt I suggest manually loading grunt-connect-proxy for now with grunt.loadNpmTasks('grunt-connect-proxy');
@dansomething Just wondering if this issue is going to be addressed. I'm having the same issue where I have to manually load grunt-connect-proxy manually (obviously something I don't need loaded with most of my grunt tasks).
@bpmckee I'm not sure it can be addressed on this end without having a deeper understanding of how jit-grunt works. Unfortunately, I'm also much too busy right now with other things. Pull requests are welcome though.
The documentation of jit-grunt
is pretty clear on how to solve this. The error-message you received is already pointing you in the right direction:
If you have installed the plugin already, please setting the static mapping.
See https://github.com/shootaroo/jit-grunt#static-mappings
If the jit-grunt
is unable to find the plugin based on the config-name, then you need to tell it where to look. This is dubbed static mapping in the jit-grunt
documentation. Please update your Gruntfile.js to include this, like so:
require('jit-grunt')(grunt, {
configureProxies: 'grunt-connect-proxy'
});
If you're also using load-grunt-config
, then you would do it like this:
require('load-grunt-config')(grunt, {
jitGrunt: {
configureProxies: 'grunt-connect-proxy'
}
}
How can I use the
configureProxies
task with jit-grunt? I'm always getting: