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
Feature request: serveStatic (for-free passthroughCopy) #12
Comments
Hmm, interesting idea! https://browsersync.io/docs/options/#option-serveStatic Has me thinking about the overlap between something like this and passthrough copy—specifically, we could expose passthrough copy directories as static dirs instead of requiring them to be copied to the output folder (during dev mode). How else do you use this one? |
That's exactly how I use it! |
We would benefit from something like this too. Having to copy thousands of image files can be quite slow. It'd be really nice if Having it support to existing api would be very helpful as older sites have a mix of directory layouts and do not have all your image/asset files in a nice top level folder. |
Thank to @zachleat and his answer to #13, I simply tried the
|
…e passthrough copy. Passthrough copy now no longer triggers a build during --serve or --watch. Instead, the Dev Server now serves these files directly from the project directory. Changes to passthrough copy files (despite skipping a build) *will* trigger a page reload in your browser. Related to 11ty/eleventy-dev-server#12 Fixes #2456
For-free passthrough copy was filed on core at 11ty/eleventy#2456 will be shipping with Eleventy 2.0.0-canary.12! Closing this one as resolved—the dev server piece of this shipped with 1.0.0-canary.11. Thank you! |
I have been using - quite a lot - the
serveStatic
feature of browsersync.Despite being "minimal", could this new server propose the same feature?
Of course it's still possible to use browsersync.
The text was updated successfully, but these errors were encountered: