pathPrefix docs
See original GitHub issueIssue Description
https://github.com/11ty/11ty-website/blob/master/src/docs/config.md
shows example config for pathPrefix as:
module.exports = {
pathPrefix: "/eleventy-base-blog/"
};
maybe should be:
module.exports = function (eleventyConfig) {
return {
pathPrefix: "/eleventy-base-blog/"
};
};
The former doesn’t work reliably.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
pathPrefix • Akka HTTP - Documentation
This directive filters incoming requests based on the part of their URI that hasn't been matched yet by other potentially existing pathPrefix or ......
Read more >Adding a Path Prefix - Gatsby
By using the Gatsby Link component, paths will automatically be prefixed with the pathPrefix value assigned in your gatsby-config.js file. If you later...
Read more >PathPrefix Property - AWS Documentation
Gets and sets the property PathPrefix. The path prefix for filtering the results. For example: CopyC#. /division_abc/subdivision_xyz/.
Read more >Routers - Traefik Labs documentation
In Traefik Proxy, a router is in charge of connecting incoming requests to the Services that can handle them. Read the technical documentation....
Read more >PathPrefix (GWT 2.6.1)
Represents the abstract path prefix that goes between the ClassPathEntry and the rest of resource's abstract path. This concept allows us to specify...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m curious as to your last comment—is there a bug there?
But I totally agree that we need to move all of the examples on
config.md
to use the API function rather than the Object. The Object is still supported but it sees very little use and is so much less powerful.The markup comment was not about the use of markup, but the fact that the raw markup was displaying on the rendered page.