-
Notifications
You must be signed in to change notification settings - Fork 754
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
basedir doesn't like relative paths up the tree? #125
Comments
I wouldn't tell you to shut up! :p But yeah, the server |
For anyone that lands on this thread - you can now do this by using the browserSync({
server: {
baseDir: "./app",
routes: {
"bower_components": "./bower_components"
}
}
}); |
👍 Thanks for following up, Shane. Clever solution. |
I can't get routes to accept an absolute path, is there something I am missing? |
I know this post is old, but I made it with this configuration: gulp.task('browserSync',function(){
browserSync.init({
startPath:'./app',
server:{
baseDir: './'
}
})
});
In my |
For example, when I use
./app
as mybaseDir
:I can't reference directories up the tree, resulting in a 404. Is there a workaround?
<script src="../bower_components/angular-route/angular-route.min.js"></script>
I mean, I get that it's not a natural server behavior to up the tree, so maybe I should just move the
bower_components
into the/app
directory and shut up. :)The text was updated successfully, but these errors were encountered: