-
-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SourceTree grunt not working #641
Comments
Error: "value" required in setHeader("Access-Control-Allow-Origin", value) at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:354:11) at ServerResponse.res.setHeader (C:\Users\carrierk\Documents\JSDev\CMV\node_modules\connect\lib\patch.js:63:22) at Object.enableCORS [as handle] (C:\Users\carrierk\Documents\JSDev\CMV\Gruntfile.js:10:11) at next (C:\Users\carrierk\Documents\JSDev\CMV\node_modules\connect\lib\proto.js:193:15) at Object.json [as handle] (C:\Users\carrierk\Documents\JSDev\CMV\node_modules\connect\lib\middleware\json.js:42:37) at next (C:\Users\carrierk\Documents\JSDev\CMV\node_modules\connect\lib\proto.js:193:15) at Object.urlencoded [as handle] (C:\Users\carrierk\Documents\JSDev\CMV\node_modules\connect\lib\middleware\urlencoded.js:40:37) at next (C:\Users\carrierk\Documents\JSDev\CMV\node_modules\connect\lib\proto.js:193:15) at Function.app.handle (C:\Users\carrierk\Documents\JSDev\CMV\node_modules\connect\lib\proto.js:201:3) at Server.app (C:\Users\carrierk\Documents\JSDev\CMV\node_modules\connect\lib\connect.js:65:37) |
I eventually got this working after making some changes to Gruntfile.js see below.
|
We should probably keep this open until it gets fixed. Pull requests welcome 😄 |
The only grunt tasks I run are |
Try running just grunt which is what I was doing once edits are saved and
web app refreshed it should reflect changes. Grunt was throwing the initial
error per documentation installation instructions anything I can do to help
repo let me know. Thanks!
…On Dec 7, 2016 7:37 PM, "Tim McGee" ***@***.***> wrote:
The only grunt tasks I run are grunt lint and grunt build so I can't
contribute to this discussion or what should go into a PR. Any PR would
need to go against the current develop branch which has other modifications
to the grunt file
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#641 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADnVNjw_6G7vTekMc3MduF66LQ0szFsWks5rF1EwgaJpZM4LCojc>
.
|
Thanks @kcarrier I know what the command is supposed to do. 😄 When I run it, I don't get that error. I think that relates to the use of a proxy page which is optional most of the time for CMV. I have never used to proxy set up the grunt so can't speak to the intent or the usage. Perhaps @DavidSpriggs can chime in with some thoughts. |
Sorry was not trying to undermine intelligence haha just trying to repo my
steps. Hope all is well brother let me know if I could be of any further
assistance.
…On Dec 7, 2016 7:59 PM, "Tim McGee" ***@***.***> wrote:
Thanks @kcarrier <https://github.com/kcarrier> I know what the command is
supposed to do. 😄 When I run it, I don't get that error. I think that
relates to the use of a proxy page which is optional most of the time for
CMV. I have never used to proxy set up the grunt so can't speak to the
intent or the usage. Perhaps @DavidSpriggs
<https://github.com/DavidSpriggs> can chime in with some thoughts.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#641 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADnVNtXQzl6bdTMr9mpMceeeZs-4BTIWks5rF1ZvgaJpZM4LCojc>
.
|
fixed in PR #669 |
All,
I have a new machine and setting up my development environment per the documentation.
When running grunt I receive this error
Path must be a string. Received null Use --force to continue
When using grunt --force I get this
Error: "value" required in setHeader("Access-Control-Allow-Origin", value)
Thoughts?
The text was updated successfully, but these errors were encountered: