-
Notifications
You must be signed in to change notification settings - Fork 123
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
Error with grunt-contrib-connect 0.8.0 #65
Comments
+1 |
As of v0.1.11 this plugin work with fine with grunt-contrib-connect 0.8.0. |
Closing since v0.1.11 is released. Please re-open if this is still an issue. |
i just encountered the same issue with downgrading to let me know if i can provide any more information to assist troubleshooting... regards, |
so... the problem didn't actually go away when using
but i continued to have other issues at runtime. it actually turned out to be operator error with this grunt config:
when i dumped the so something like what the author of this post shown below would be the real solution to the issue:
regards, |
Perfect life saver! Thanks Tony. |
Tony! n1. Thank you. |
Whee! Is still broken btw. Will try the workaround. |
This plugin is broken in usage with grunt connect 0.8.0, updating to this version will result in the following error:
Running "connect:devproxy" (connect) task
Verifying property connect.devproxy exists in config...OK
File: [no files]
Options: protocol="http", port=9997, hostname="closedhost", base="tmp", directory=null, keepalive=false, debug=false, livereload, open=false, useAvailablePort=false,onCreateServer=null, middleware=undefined
Warning: Arguments to path.resolve must be strings Use --force to continue.
Please fix. :)
Best Regards,
@zenhunt
The text was updated successfully, but these errors were encountered: