![dependabot-preview[bot]](https://avatars.githubusercontent.com/in/2141?v=4&s=144)
Commit activity
Last 12 weeks · 0 commits
Community health
5 of 6 standards met
75
✓README✓License✓Contributing✓Code of Conduct○Issue Template✓PR Template
Recent PRs & issues
Quiet · Last activity 1y ago
See all on GitHub →
I noticed that navigating between pages via the prev/next buttons or sidebar links keeps the scroll position from the previous page, which is disorienting. For example, scrolling to the bottom of one page and clicking "Getting Started" in the footer lands you at the bottom of the new page instead of the top. The router's built-in scrollBehavior returns but doesn't always fire correctly with async page components. I added explicit scroll handling in the Layout's afterEach hook - it checks if the path actually changed (ignoring hash-only navigation) and scrolls to top after the DOM updates via $nextTick. Tested locally by clicking through the sidebar and prev/next navigation - pages now consistently start from the top. Fixes #2156
Hi there, I'm reaching out because vuepress is one of the most depended-on npm packages that runs an install script, and an accepted npm RFC is going to change how those scripts behave. The RFC blocks dependency install scripts by default during . That's the same thing pnpm, Yarn Berry, Bun, and Deno already do. Users opt back in per package through a new field in (or the command). The motivation is the run of supply-chain attacks over the last couple of years that used hooks to run code the moment a package landed in the tree. For vuepress, the script that's affected is: "postinstall": "opencollective-postinstall exit 0" That script is written to fail quietly and looks non-essential, so for most users blocking it changes nothing. No action is likely needed on your side. The one thing worth doing is a quick check that nothing important silently depends on it running, and if it does, documenting the line in your README. I wanted to flag this early so you've got time to plan rather than find out when the install warnings start showing up. The full RFC is here: https://github.com/npm/rfcs/pull/868. Happy to answer any questions.
Feature request If there was a feature to build with relative urls, we could run the files without opening a server. Might be something like: And urls would be like: instead of: What problem does this feature solve? Run static files without a server. Are you willing to work on this yourself?** Sure.
Recent fixes
When we do theme customization, we often need to define routes for some pages. When I redefine the route for the 404 page, I found that it didn't work. I don't have the part I defined in the router instance. I feel very strange. I enhanced the Vue instance with the enhancementApp.js file in the theme, where the code for the route enhancement section is: No matter how I define it, path: '*' seems to be overwritten by GlobalLayout.vue. Is there a solution to this problem?
Summary What kind of change does this PR introduce? (check at least one) [ ] Bugfix [ ] Feature [ ] Code style update [ ] Refactor [ x] Docs [ ] Build-related changes [ ] Other, please describe: If changing the UI of default theme, please provide the before/after screenshot: Does this PR introduce a breaking change? (check one) [ ] Yes [ x] No If yes, please describe the impact and migration path for existing applications: The PR fulfills these requirements: [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. , where "xxx" is the issue number) You have tested in the following browsers: (Providing a detailed version will be better.) [ ] Chrome [ ] Firefox [ ] Safari [ ] Edge [ ] IE If adding a new feature, the PR's description includes: [ ] A convincing reason for adding this feature [ ] Related documents have been updated [ ] Related tests have been updated To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it. Other information:** Hi there! I've been working on a static site hosting service with a bit of a twist, we provide an interface and version control to static pages with immediate publishing/unpublishing workflow support to blend static sites with traditional dynamic content management systems. We want to support open-source by providing the service for free to open-source projects. Hoping that we can including some information to support a different deployment target for the static output of vuepress! I've set up a boilerplate example to show off using vuepress+quantcdn! https://github.com/quantcdn/quant-vuepress-example ab819485-1f89-478e-a63f-a752a63f3eee-vuepress-example.quantcdn.io
Summary Added no SSR build support What kind of change does this PR introduce? (check at least one) [ ] Bugfix [x] Feature [ ] Code style update [ ] Refactor [ ] Docs [ ] Build-related changes [ ] Other, please describe: If changing the UI of default theme, please provide the before/after screenshot: Does this PR introduce a breaking change? (check one) [x] Yes [ ] No If yes, please describe the impact and migration path for existing applications: The PR fulfills these requirements: [x] When resolving a specific issue, it's referenced in the PR's title (e.g. , where "xxx" is the issue number) You have tested in the following browsers: (Providing a detailed version will be better.) [x] Chrome [ ] Firefox [ ] Safari [ ] Edge [ ] IE If adding a new feature, the PR's description includes: [x] A convincing reason for adding this feature [ ] Related documents have been updated [ ] Related tests have been updated To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it. Other information:**
Structured data for AI agents
Repository: vuejs/vuepress. Description: 📝 Minimalistic Vue-powered static site generator Stars: 22754, Forks: 4635. Primary language: JavaScript. Languages: JavaScript (55.3%), TypeScript (22%), Vue (19.7%), Stylus (2.7%), HTML (0.2%). License: MIT. Homepage: https://vuepress.vuejs.org Topics: blog-engine, docs-generator, seo, static-site-generator, vue, vuepress. Latest release: v1.9.10 (2y ago). Open PRs: 67, open issues: 540. Last activity: 1y ago. Community health: 75%. Top contributors: ulivz, yyx990803, meteorlxy, bencodezen, shigma, billyyyyy3320, kefranabg, dependabot-preview[bot], ycmjason, d-pollard and others.