5 of 6 standards met
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
Repository: vuejs/vuepress. Description: 📝 Minimalistic Vue-powered static site generator Stars: 22813, Forks: 4676. 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: 66, open issues: 541. Last activity: 1y ago. Community health: 75%. Top contributors: ulivz, yyx990803, meteorlxy, bencodezen, shigma, billyyyyy3320, kefranabg, dependabot-preview[bot], ycmjason, d-pollard and others.
JavaScript
Last 12 weeks · 0 commits
Yarn 4.9.2 ✔ Initializing and preparing data - done in 83ms x Build failed in 2.50s ✖ Compiling with vite - failed in 4.44s error .yarn/__virtual__/@vuepress-highlighter-helper-virtual-11f96e484f/0/cache/@vuepress-highlighter-helper-npm-2.0.0-rc.85-a48ad3cc24-e51c339362.zip/node_modules/@vuepress/highlighter-helper/lib/client/composables/setupCollapsedLines.js (1:9): "useEventListener" is not exported by "__vite-optional-peer-dep:@vueuse/core:@vuepress/highlighter-helper", imported by ".yarn/__virtual__/@vuepress-highlighter-helper-virtual-11f96e484f/0/cache/@vuepress-highlighter-helper-npm-2.0.0-rc.85-a48ad3cc24-e51c339362.zip/node_modules/@vuepress/highlighter-helper/lib/client/composables/setupCollapsedLines.js". file: D:/github/vuepress-starter/.yarn/__virtual__/@vuepress-highlighter-helper-virtual-11f96e484f/0/cache/@vuepress-highlighter-helper-npm-2.0.0-rc.85-a48ad3cc24-e51c339362.zip/node_modules/@vuepress/highlighter-helper/lib/client/composables/setupCollapsedLines.js:1:9 1: import { useEventListener } from '@vueuse/core'; ^ 2: export const setupCollapsedLines = ({ selector = 'div[class*="language-"].has-collapsed-lines > .collapsed-lines', } ... 3: useEventListener('click', (e) => {
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:**
Summary What kind of change does this PR introduce? (check at least one) [ ] Bugfix [x] 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: [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 [x] Safari [ ] Edge [ ] IE If adding a new feature, the PR's description includes: [x] A convincing reason for adding this feature [x] 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:** fixes #1959