profile
viewpoint
ULIVZ ulivz Alipay Hangzhou, China ulivz.com @vuejs team member, focus on VuePress and its ecology.
MemberEvent

push eventvuejs/vuepress

xr0master

commit sha 120d88589a88a52fa67e788b838350096ae5c843

feat($core): use any custom protocol for outboundRE (#1731)

view details

push time in 7 days

PR merged vuejs/vuepress

fix(Util): use any custom protocol for outboundRE

Little improvement for vuejs#1677

I think we can use any custom protocol for external link.

+1 -1

0 comment

1 changed file

xr0master

pr closed time in 7 days

pull request commentvuejs/vuepress

workflow: add CONTRIBUTING.md

@f3ltron Is this pull request ready?

ulivz

comment created time in 7 days

push eventulivz/awesome-vuepress

ntnyq

commit sha cf2405d41e67a8f77733a395d6623b35230587e2

feat: add social share plugin (#49)

view details

push time in 7 days

startedntnyq/vuepress-plugin-social-share

started time in 7 days

push eventulivz/awesome-vuepress

Bobby DeSimone

commit sha 196a234f2eb50f02205a72c293a0b18894545da6

feat: add pomerium (#50)

view details

push time in 7 days

PR merged ulivz/awesome-vuepress

Add pomerium

❤️ Vuepress

+1 -0

0 comment

1 changed file

desimone

pr closed time in 7 days

push eventulivz/awesome-vuepress

Vinyas Malagaudanavar

commit sha c352ef56baf7102e04e0bf2131849d1b272b4a08

fix: broken link for KTQUEZ theme (#51)

view details

push time in 7 days

pull request commentumijs/umi

feat: add env CLEAR_OUTPUT

CI 过了,好像覆盖率不够 ... 这个要写单测吗?

ulivz

comment created time in 10 days

PR opened umijs/umi

feat: do not exit process when build is under watch mode

<!-- Thank you for your pull request. Please review below requirements. Bug fixes and new features should include tests. Contributors guide: https://github.com/umijs/umi/blob/master/CONTRIBUTING.md

感谢您贡献代码。请确认下列 checklist 的完成情况。 Bug 修复和新功能必须包含测试。 Contributors guide: https://github.com/umijs/umi/blob/master/CONTRIBUTING.md -->

Checklist

<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

  • [ ] npm test passes
  • [ ] tests are included
  • [ ] documentation is changed or added
  • [x] commit message follows commit guidelines
Description of change

<!-- Provide a description of the change below this comment. -->

  • any feature?

umi shouldn't exit current build process when users enable watch under build.

  • close https://github.com/umijs/umi/ISSUE_URL
+6 -1

0 comment

1 changed file

pr created time in 10 days

push eventulivz/umi

ULIVZ

commit sha 6b39355636e320c710f558a4fcf2b831d04d1d29

feat: do not exit process when build is under watch mode

view details

push time in 10 days

push eventulivz/umi

ULIVZ

commit sha 0a4c24d261353e319df769720f245d797a38e6b7

feat: do not exit process when build is under watch mode

view details

push time in 10 days

create barnchulivz/umi

branch : feat/do-not-exit-under-watch

created branch time in 10 days

push eventulivz/umi

ULIVZ

commit sha 818471b8374f89cff6ae4d4f50dc31662c01befc

Merge branch 'master' into feat/new-env-UMI_DO_NOT_CLEAN_OUTPUT

view details

push time in 10 days

push eventulivz/umi

chencheng

commit sha 8e59d34f0d39c5ffe8eed3398587c85a3feb9f02

chore: update label-actions.yml

view details

chencheng (云谦)

commit sha 97e88e112acf9500c72c36a6ad5ce9370dda95ef

Revert "fix: LocaleProvider warning after antd@3.21 (#2941)" (#2992) This reverts commit e35aaaa25c60a8a9f30871c7751565a073648014.

view details

chencheng

commit sha 5e1b507e8916e6d5cca23bd30b7eca089eeef824

Publish - umi-plugin-locale@2.9.11 - umi-plugin-react@1.9.17

view details

ULIVZ

commit sha a1cad3cab8b600d2f38dacd26932fccaa8f84a0d

feat: expose internal "styleLoader" option. (#3000)

view details

信鑫-King

commit sha aacad0d6dc6c6b78ed861254ea1a302c1546cc66

fix: antd ConfigProvider not found (#2993) * fix: antd ConfigProvider not found * fix: test * feat: test

view details

信鑫-King

commit sha cd707bd5644eab1c0ecaf617c10061f9da0b554b

feat: locale baseSeparator (#2983) * feat: locale baseSeparator * fix: use string * feat: locale baseSeparator * fix: use string * test: baseSeparator locale cases * test: e2e locale test * test: only * fix: appLocale * fix: locale react-intl use - * test: e2e locale test * fix: test * :memo: docs * fix: sk lang test case * fix: test case

view details

ULIVZ

commit sha 0f4dcfdce75653988dfe903f4401487e52e3cd5e

Merge branch 'master' into feat/new-env-UMI_DO_NOT_CLEAN_OUTPUT

view details

push time in 10 days

PR opened umijs/umi

feat: expose internal "styleLoader" option.

<!-- Thank you for your pull request. Please review below requirements. Bug fixes and new features should include tests. Contributors guide: https://github.com/umijs/umi/blob/master/CONTRIBUTING.md

感谢您贡献代码。请确认下列 checklist 的完成情况。 Bug 修复和新功能必须包含测试。 Contributors guide: https://github.com/umijs/umi/blob/master/CONTRIBUTING.md -->

Checklist

<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

  • [x] npm test passes
  • [ ] tests are included
  • [ ] documentation is changed or added
  • [x] commit message follows commit guidelines
Description of change

<!-- Provide a description of the change below this comment. -->

  • any feature?

Giving the ability for users to quickly leverage style-loader instead of mini-extract-css-plugin.

Users'll have 3 ways to enable and modify the options of style-loader without using chanWebpack:

1 .umirc.js

module.exports = {
   styleLoader: {}
}

2 Plugin API - modifyAFWebpackOpts

 api.modifyAFWebpackOpts(memo => {
      return Object.assign(memo, {
        styleLoader: {}
      })
    })

3 Plugin API - modifyDefaultConfig

 api.modifyDefaultConfig(memo => {
      return Object.assign(memo, {
        styleLoader: {}
      })
    })

Why umi configurations can be used to configure af-webpack

https://github.com/umijs/umi/blob/5e1b507e8916e6d5cca23bd30b7eca089eeef824/packages/umi-build-dev/src/plugins/afwebpack-config/index.js#L135-L137


  • close https://github.com/umijs/umi/2320

Since style-loader has reach 1.0.0: https://github.com/webpack-contrib/style-loader/blob/master/CHANGELOG.md#100-2019-08-06

The style-loader/useable loader was removed in favor injectType option (look the documentation about the injectType option)

Once we upgrade to 1.0.0, for #2320 we can just configure like this:

module.exports = {
   styleLoader: {
       injectType: 'lazyStyleTag'
   }
}

ref: https://github.com/webpack-contrib/style-loader#lazystyletag

+14 -0

0 comment

1 changed file

pr created time in 10 days

create barnchulivz/umi

branch : feat/expose-styleLoader-option

created branch time in 10 days

pull request commentumijs/umi

feat: add env UMI_DO_NOT_CLEAN_OUTPUT

好的,我看了下之前的命名,好像都是用的 CLEAR,就先用 CLEAR_OUTPUT 了,文档也更新了。

ulivz

comment created time in 10 days

push eventulivz/umi

ULIVZ

commit sha d08c411c8c87404ac537ed685ee92f2ca5b2a13b

feat: add env CLEAR_OUTPUT

view details

push time in 10 days

push eventulivz/umi

ULIVZ

commit sha 9ddb69845e58865011c20a6b03b2935dadb59019

feat: add env UMI_DO_NOT_CLEAN_OUTPUT

view details

push time in 11 days

PR opened umijs/umi

feat: add env UMI_DO_NOT_CLEAN_OUTPUT

<!-- Thank you for your pull request. Please review below requirements. Bug fixes and new features should include tests. Contributors guide: https://github.com/umijs/umi/blob/master/CONTRIBUTING.md

感谢您贡献代码。请确认下列 checklist 的完成情况。 Bug 修复和新功能必须包含测试。 Contributors guide: https://github.com/umijs/umi/blob/master/CONTRIBUTING.md -->

Checklist

<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

  • [x] npm test passes
  • [x] tests are included
  • [ ] documentation is changed or added
  • [x] commit message follows commit guidelines
Description of change

<!-- Provide a description of the change below this comment. -->

  • any feature?

Add a new env UMI_DO_NOT_CLEAN_OUTPUT to tell build process not to remove the dist files.

  • close https://github.com/umijs/umi/issues/2448
+5 -3

0 comment

1 changed file

pr created time in 11 days

create barnchulivz/umi

branch : feat/new-env-UMI_DO_NOT_CLEAN_OUTPUT

created branch time in 11 days

MemberEvent

startedyoungtailors/vuepress-plugin-component-docgen

started time in 17 days

push eventvuejs/vuepress

Sarah Dayan

commit sha 8039f421f7525852daf2dc5787c19fea19659242

docs: documentation linting (#1745) * chore: install textlint * chore: add textlint rules * feat: set up configuration file and command * fix: run textlint on files * chore: lint .textlintrc.js * chore: add custom terms * chore: add comment filter * fix: fix frontmatter term * chore: set subjective rules to warning severity * fix: manually fix issues * chore: add script as pre-commit hook

view details

push time in 18 days

PR merged vuejs/vuepress

feat: documentation linting docs

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

This PR adds content linting to the documentation of VuePress, using textlint.

Some rules (the more subjective ones) are set with a warning severity, meaning they wouldn't make a CI fail. It also leaves the possibility of progressively fixing things.

The PR is quite large because it also embarks a first run at fixing issues that were revealed by textlint.

What kind of change does this PR introduce? (check at least one)

  • [ ] Bugfix
  • [ ] Feature
  • [ ] Code style update
  • [ ] Refactor
  • [x] Docs
  • [x] 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

Other information:

Content linting was added as a pre-commit hook. I changed the way the other pre-commit hook was wired so the whole thing works properly across the monorepo.

Question: for now, the linting precommit hooks are split into two:

  • a local one in docs/ (the one created in this PR)
  • a global one at the root (to lint JavaScript and Vue files)

They're triggered by running the global precommit first, then the local ones with lerna run. Ideally, it's better to have a command per repo. Do we think it's worth it?

+1232 -261

1 comment

36 changed files

sarahdayan

pr closed time in 18 days

push eventvuejs/vuepress

ntnyq

commit sha f6a2fb9f72a84eb4da9092a75eeb806abcb72946

docs: fix typo (#1742)

view details

push time in 18 days

PR merged vuejs/vuepress

docs: fix typo docs docs-language:ch

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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. fix #xxx[,#xxx], 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:

+8 -8

0 comment

2 changed files

ntnyq

pr closed time in 18 days

push eventvuejs/vuepress

Eduardo San Martin Morote

commit sha 0eafea9c593f924e597cbfbd7503184eeaf10843

chore: remove next badge from readme (#1746)

view details

Jen Looper

commit sha d50fa1bc17c02d32db0f13900f857da60dd39ae6

docs: adding all-contributors table for core team members (#1744) * adding all-contributors table for core team members * chore: add self to core contributors * Add Franck to core contributors * chore: add @sobolevn to core contributors

view details

ULIVZ

commit sha 8f68fe8e4ccaffad9bb4f32ce3d0fb518ff62f31

Merge branch 'master' into feat/doc-linting

view details

push time in 18 days

push eventvuejs/vuepress

Jen Looper

commit sha d50fa1bc17c02d32db0f13900f857da60dd39ae6

docs: adding all-contributors table for core team members (#1744) * adding all-contributors table for core team members * chore: add self to core contributors * Add Franck to core contributors * chore: add @sobolevn to core contributors

view details

push time in 18 days

PR merged vuejs/vuepress

adding all-contributors table for core team members docs

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], 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:

  • [ ] 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:

This PR adds a grid for Core Team members to add themselves and their capacities as Core members. Other members can add themselves to .all-contributorsrc and then regenerate the grid on the README.md file via yarn all-contributors generate

+97 -2

1 comment

3 changed files

jlooper

pr closed time in 18 days

pull request commentvuejs/vuepress

adding all-contributors table for core team members

Just merged this pull request, if there are new members, feel free to submit PR ~

jlooper

comment created time in 18 days

issue closedvuejs/vuepress

Enable CI build for forked Pull Requests

Feature request

CI process is not fired for forked pull requests. It means no CI for external contributors 😭

We should turn on this on CircleCI:

Capture d’écran 2019-08-06 à 11 30 20

Are you willing to work on this yourself?

I don't think I have permission on CircleCI for now 😄

closed time in 18 days

kefranabg

issue commentvuejs/vuepress

Enable CI build for forked Pull Requests

Wow, cool! I just open it.

image

kefranabg

comment created time in 18 days

push eventulivz/markdown-it-chain

greenkeeper[bot]

commit sha ae3e337f938f445c08d7131d268aabc6d659e8ea

Update dependencies to enable Greenkeeper 🌴 (#6) * chore(package): update dependencies * docs(readme): add Greenkeeper badge

view details

push time in 18 days

PR merged ulivz/markdown-it-chain

Update dependencies to enable Greenkeeper 🌴 greenkeeper

Let’s get started with automated dependency management for markdown-it-chain :muscle:

🔒 Greenkeeper has found a yarn.lock file in this repository. Greenkeeper supports lockfile updates for public packages. If you use private packages in your repository, please use greenkeeper-lockfile to make sure these can get updated as well.

This pull request updates all your dependencies to their latest version. Having them all up to date really is the best starting point for keeping up with new releases. Greenkeeper will look out for further dependency updates and make sure to handle them in isolation and in real-time, but only after you merge this pull request.

Important: Greenkeeper will only start watching this repository’s dependency updates after you merge this initial pull request.


<details> <summary>💥 Tests on this branch are failing. Here’s how to proceed.</summary>

To solve the issue, first find out which of the dependency’s updates is causing the problem. Then fix your code to accomodate the changes in the updated dependency. next-update is a really handy tool to help you with this.

Then push your changes to this branch and merge it. </details> <details> <summary>🏷 How to check the status of this repository</summary>

Greenkeeper adds a badge to your README which indicates the status of this repository.

This is what your badge looks like right now :point_right: Greenkeeper badge </details> <details> <summary>🙈 How to ignore certain dependencies</summary>

You may have good reasons for not wanting to update to a certain dependency right now. In this case, you can change the dependency’s version string in the package.json file back to whatever you prefer.

To make sure Greenkeeper doesn’t nag you again on the next update, add a greenkeeper.ignore field to your package.json, containing a list of dependencies you don’t want to update.

// package.json
{
  …
  "greenkeeper": {
    "ignore": [
      "package-names",
      "you-want-me-to-ignore"
    ]
  }
}

</details> <details> <summary>👩‍💻 How to update this pull request</summary>

  # Change into your repository’s directory
  git fetch --all
  git checkout greenkeeper/initial
  npm install-test
  # Adapt your code until everything works again
  git commit -m 'chore: adapt code to updated dependencies'
  git push https://github.com/ulivz/markdown-it-chain.git greenkeeper/initial

</details> <details> <summary>✨ How do dependency updates work with Greenkeeper?</summary>

After you merge this pull request, Greenkeeper will create a new branch whenever a dependency is updated, with the new version applied. The branch creation should trigger your testing services and check whether your code still works with the new dependency version. Depending on the the results of these tests Greenkeeper will try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date.

-  "underscore": "^1.6.0"
+  "underscore": "^1.7.0"

The above example shows an in-range update. 1.7.0 is included in the old ^1.6.0 range, because of the caret ^ character . When the test services report success Greenkeeper will silently delete the branch again, because no action needs to be taken – everything is fine.

However, should the tests fail, Greenkeeper will create an issue to inform you about the problem immediately.

This way, you’ll never be surprised by a dependency breaking your code. As long as everything still works, Greenkeeper will stay out of your way, and as soon as something goes wrong, you’ll be the first to know.

-  "lodash": "^3.0.0"
+  "lodash": "^4.0.0"

In this example, the new version 4.0.0 is not included in the old ^3.0.0 range. For version updates like these – let’s call them “out of range” updates – you’ll receive a pull request.

This means that you no longer need to check for new versions manually – Greenkeeper will keep you up to date automatically.

These pull requests not only serve as reminders to update: If you have solid tests and good coverage, and the pull requests passes those tests, you can very likely just merge it and release a new version of your software straight away :shipit:

To get a better idea of which ranges apply to which releases, check out the extremely useful semver calculator provided by npm. </details> <details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>


Good luck with your project and see you soon :sparkles:

Your Greenkeeper bot :palm_tree:

+9 -7

1 comment

2 changed files

greenkeeper[bot]

pr closed time in 18 days

push eventulivz/template-vuepress

greenkeeper[bot]

commit sha 2821fa9888b0627f14ec34ba23daa150be2fce42

chore: add Greenkeeper config file

view details

greenkeeper[bot]

commit sha c3aacde713479038401fbc1e56eb77210bffccfa

chore(package): update dependencies

view details

greenkeeper[bot]

commit sha 8597578fd8be378ae19a235619b33f964b415324

docs(readme): add Greenkeeper badge

view details

ULIVZ

commit sha 6770f82fbe9d13b2e3718d81ecfbcf60bceaa56d

Merge pull request #3 from ulivz/greenkeeper/initial Update dependencies to enable Greenkeeper 🌴

view details

push time in 18 days

PR merged ulivz/template-vuepress

Update dependencies to enable Greenkeeper 🌴 greenkeeper

Let’s get started with automated dependency management for template-vuepress :muscle:

🔒 Greenkeeper has found a yarn.lock file in this repository. Greenkeeper supports lockfile updates for public packages. If you use private packages in your repository, please use greenkeeper-lockfile to make sure these can get updated as well.

This pull request updates all your dependencies to their latest version. Having them all up to date really is the best starting point for keeping up with new releases. Greenkeeper will look out for further dependency updates and make sure to handle them in isolation and in real-time, but only after you merge this pull request.

Important: Greenkeeper will only start watching this repository’s dependency updates after you merge this initial pull request.

📦 📦 Greenkeeper has detected multiple package.json files. They have all been added to a new greenkeeper.json config file. They’ve been collected in a group called default, meaning that all of them will receive updates together. You can rename, add and remove groups and freely assign each package.json to whichever group you like. It’s common, for example, to have one frontend group and one backend group, each with a couple of package.json files. In any case, all files in a group will have their updates collected into single PRs and issues.


<details> <summary>💥 Tests on this branch are failing. Here’s how to proceed.</summary>

To solve the issue, first find out which of the dependency’s updates is causing the problem. Then fix your code to accomodate the changes in the updated dependency. next-update is a really handy tool to help you with this.

Then push your changes to this branch and merge it. </details> <details> <summary>🏷 How to check the status of this repository</summary>

Greenkeeper adds a badge to your README which indicates the status of this repository.

This is what your badge looks like right now :point_right: Greenkeeper badge </details> <details> <summary>🙈 How to ignore certain dependencies</summary>

You may have good reasons for not wanting to update to a certain dependency right now. In this case, you can change the dependency’s version string in the package.json file back to whatever you prefer.

To make sure Greenkeeper doesn’t nag you again on the next update, add a greenkeeper.ignore field to your package.json, containing a list of dependencies you don’t want to update.

// package.json
{
  …
  "greenkeeper": {
    "ignore": [
      "package-names",
      "you-want-me-to-ignore"
    ]
  }
}

</details> <details> <summary>👩‍💻 How to update this pull request</summary>

  # Change into your repository’s directory
  git fetch --all
  git checkout greenkeeper/initial
  npm install-test
  # Adapt your code until everything works again
  git commit -m 'chore: adapt code to updated dependencies'
  git push https://github.com/ulivz/template-vuepress.git greenkeeper/initial

</details> <details> <summary>✨ How do dependency updates work with Greenkeeper?</summary>

After you merge this pull request, Greenkeeper will create a new branch whenever a dependency is updated, with the new version applied. The branch creation should trigger your testing services and check whether your code still works with the new dependency version. Depending on the the results of these tests Greenkeeper will try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date.

-  "underscore": "^1.6.0"
+  "underscore": "^1.7.0"

The above example shows an in-range update. 1.7.0 is included in the old ^1.6.0 range, because of the caret ^ character . When the test services report success Greenkeeper will silently delete the branch again, because no action needs to be taken – everything is fine.

However, should the tests fail, Greenkeeper will create an issue to inform you about the problem immediately.

This way, you’ll never be surprised by a dependency breaking your code. As long as everything still works, Greenkeeper will stay out of your way, and as soon as something goes wrong, you’ll be the first to know.

-  "lodash": "^3.0.0"
+  "lodash": "^4.0.0"

In this example, the new version 4.0.0 is not included in the old ^3.0.0 range. For version updates like these – let’s call them “out of range” updates – you’ll receive a pull request.

This means that you no longer need to check for new versions manually – Greenkeeper will keep you up to date automatically.

These pull requests not only serve as reminders to update: If you have solid tests and good coverage, and the pull requests passes those tests, you can very likely just merge it and release a new version of your software straight away :shipit:

To get a better idea of which ranges apply to which releases, check out the extremely useful semver calculator provided by npm. </details> <details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>


Good luck with your project and see you soon :sparkles:

Your Greenkeeper bot :palm_tree:

+14 -2

1 comment

3 changed files

greenkeeper[bot]

pr closed time in 18 days

startedFormidableLabs/react-live

started time in 18 days

startedIdered/Editr.js

started time in 18 days

startedvue-styleguidist/vuepress-plugin-live

started time in 18 days

startedvuejs/jsx

started time in 19 days

push eventvuejs/vuepress

Eduardo San Martin Morote

commit sha 0eafea9c593f924e597cbfbd7503184eeaf10843

chore: remove next badge from readme (#1746)

view details

push time in 19 days

PR merged vuejs/vuepress

chore: remove next badge from readme

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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. fix #xxx[,#xxx], 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:

+0 -1

0 comment

1 changed file

posva

pr closed time in 19 days

MemberEvent
MemberEvent
MemberEvent
MemberEvent

push eventvuejs/vuepress

Billyyyyy3320

commit sha 93a1ec05cc36b8c9c5dbdad2841b9b5c563f16b8

chore: fix script typo (#1740)

view details

push time in 20 days

PR merged vuejs/vuepress

fix: fix script typo

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

What kind of change does this PR introduce? (check at least one)

  • [x] Bugfix
  • [ ] 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)

  • [ ] 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. fix #xxx[,#xxx], 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:

  • [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:

+1 -1

0 comment

1 changed file

newsbielt703

pr closed time in 20 days

MemberEvent
MemberEvent

pull request commentulivz/vuepress-theme-blog

fix: fix config for summary, summaryLength and pwa

Note that the better commit message would be:

fix: config for summary, summaryLength and pwa (close: #13)(#14)

Whatever that's a great pull request, Thanks!

newsbielt703

comment created time in 20 days

push eventulivz/vuepress-theme-blog

Billyyyyy3320

commit sha 7d40fe34a8f65057ff4ce3e26007d6c260ce127d

fix: config for summary, summaryLength and pwa (close: #13)(#14) fix #13

view details

push time in 20 days

PR merged ulivz/vuepress-theme-blog

fix: fix config for summary, summaryLength and pwa

fix #13

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

What kind of change does this PR introduce? (check at least one)

  • [x] Bugfix
  • [ ] 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)

  • [ ] 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. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

  • [x] Chrome
  • [x] Firefox
  • [x] 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:

+3 -4

0 comment

1 changed file

newsbielt703

pr closed time in 20 days

issue closedulivz/vuepress-theme-blog

Can't hide summary by setting option summary to false

<!-- Please don't delete this template or we'll close your issue --> <!-- Before creating an issue please make sure you are using the latest version of VuePress. -->

<!-- Please confirm you will submit an issue. --> <!-- Issues which contain questions or support requests will be closed. --> <!-- (Update "[ ]" to "[x]" to check a box) -->

I confirm that this is an issue rather than a question.

<!-- Please ask questions via following several ways. --> <!-- https://vue-land.js.org/ --> <!-- https://forum.vuejs.org/ --> <!-- https://stackoverflow.com/questions/ask?tags=vuepress -->

Bug report

Steps to reproduce

<!-- Please choose one of the following and and fill in the information. --> <!-- (Update "[ ]" to "[x]" to check a box) -->

<!-- If you are reporting a bug that can ONLY be reproduced on your repository, PLEASE provide this repo link. That takes guessing work out of the way and saves us time. --> <!-- If your repo isn't public, you can use codesandbox or yarn create vuepress to create a minimal reproduction -->

I prepared a reproduction repo, here is the reproduction repo: codesandbox

What is expected?

Hide summary.

What is actually happening?

Hide nothing.

Other relevant information

closed time in 20 days

newsbielt703

PR opened vuejs/vuepress

workflow: add CONTRIBUTING.md

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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. fix #xxx[,#xxx], 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:

+78 -0

0 comment

1 changed file

pr created time in 20 days

push eventvuejs/vuepress

ULIVZ

commit sha 64cffca832659a9e1fe0a5b4d9d011643c215601

workflow: add CONTRIBUTING.md

view details

push time in 20 days

push eventvuejs/vuepress

ULIVZ

commit sha 1505b46103096b46e5a86f44f93f2b5f02806fa7

workflow: add CONTRIBUTING.md

view details

push time in 20 days

create barnchvuejs/vuepress

branch : feat/add-contributing-guide

created branch time in 20 days

issue openedvuejs/vuepress

Update the domain setting to docuementation

<!-- Please don't delete this template or we'll close your issue --> <!-- Before creating an issue please make sure you are using the latest version of VuePress. -->

Feature request

<!-- Please ask questions on StackOverflow. --> <!-- https://stackoverflow.com/questions/ask?tags=vuepress --> <!-- Issues which contain questions or support requests will be closed. -->

Since 1.x is stable enough, it's time to use vuepress.vuejs.org to host the latest documentation, while v0.vuepress.vuejs.org could be used for the docs of 0.x.

Note that after this change, the v1.vuepress.vuejs.org should be CNAME or redirected to vuepress.vuejs.org.

What problem does this feature solve?

User can see the latest documentation with the short website link.

What does the proposed API look like?

N/A

How should this be implemented in your opinion?

N/A

Are you willing to work on this yourself?

N/A

created time in 20 days

push eventvuejs/vuepress

Jen Looper

commit sha 3b87a54354829a86440827aa7f16a4e5be6a33c0

Create CODE_OF_CONDUCT.md (#1736)

view details

push time in 20 days

PR merged vuejs/vuepress

Create CODE_OF_CONDUCT.md

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

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:

  • [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], 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:

+76 -0

0 comment

1 changed file

jlooper

pr closed time in 20 days

MemberEvent
MemberEvent
MemberEvent

startedDivanteLtd/storefront-ui

started time in 21 days

push eventulivz/timeout-wrap

greenkeeper[bot]

commit sha 8b3c04038dbe5d901b220ee0629c2e2aeb9c0378

chore(package): update release-it to version 12.3.5 (#2)

view details

push time in 21 days

PR merged ulivz/timeout-wrap

Update release-it to the latest version 🚀 greenkeeper

The devDependency release-it was updated from 12.3.4 to 12.3.5.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


Publisher: webpro License: MIT

<details> <summary>Release Notes for Release 12.3.5</summary>

<ul> <li>Fix bug in argument replacement for Windows (<a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/release-it/release-it/commit/c349342af809cb32db4ca572495cf682d4635af3/hovercard" href="https://urls.greenkeeper.io/release-it/release-it/commit/c349342af809cb32db4ca572495cf682d4635af3"><tt>c349342</tt></a>)</li> <li>Fix up tests and increase coverage for Log module (<a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/release-it/release-it/commit/406a23b73b8a8c9004d1bac41ae4ea0415bbc6cc/hovercard" href="https://urls.greenkeeper.io/release-it/release-it/commit/406a23b73b8a8c9004d1bac41ae4ea0415bbc6cc"><tt>406a23b</tt></a>)</li> <li>Increase coverage for Git plugin (<a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/release-it/release-it/commit/a88bcd46a25cbcddabed87b41719b468b4e3f93a/hovercard" href="https://urls.greenkeeper.io/release-it/release-it/commit/a88bcd46a25cbcddabed87b41719b468b4e3f93a"><tt>a88bcd4</tt></a>)</li> <li>Increase consistency in docs (<a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/release-it/release-it/commit/1901fbbdbf0ba08b9e8873c5f8a7af6687056ada/hovercard" href="https://urls.greenkeeper.io/release-it/release-it/commit/1901fbbdbf0ba08b9e8873c5f8a7af6687056ada"><tt>1901fbb</tt></a>)</li> <li>Move Git and Pre-releases sections to separate doc (<a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/release-it/release-it/commit/918180def5035fcf22588efb7a252756f5c6eb68/hovercard" href="https://urls.greenkeeper.io/release-it/release-it/commit/918180def5035fcf22588efb7a252756f5c6eb68"><tt>918180d</tt></a>)</li> </ul> </details>

<details> <summary>Commits</summary> <p>The new version differs by 6 commits.</p> <ul> <li><a href="https://urls.greenkeeper.io/release-it/release-it/commit/f513d22197e42f25cb6cde6b8519937a65bb6513"><code>f513d22</code></a> <code>Release 12.3.5</code></li> <li><a href="https://urls.greenkeeper.io/release-it/release-it/commit/c349342af809cb32db4ca572495cf682d4635af3"><code>c349342</code></a> <code>Fix bug in argument replacement for Windows</code></li> <li><a href="https://urls.greenkeeper.io/release-it/release-it/commit/406a23b73b8a8c9004d1bac41ae4ea0415bbc6cc"><code>406a23b</code></a> <code>Fix up tests and increase coverage for Log module</code></li> <li><a href="https://urls.greenkeeper.io/release-it/release-it/commit/a88bcd46a25cbcddabed87b41719b468b4e3f93a"><code>a88bcd4</code></a> <code>Increase coverage for Git plugin</code></li> <li><a href="https://urls.greenkeeper.io/release-it/release-it/commit/1901fbbdbf0ba08b9e8873c5f8a7af6687056ada"><code>1901fbb</code></a> <code>Increase consistency in docs</code></li> <li><a href="https://urls.greenkeeper.io/release-it/release-it/commit/918180def5035fcf22588efb7a252756f5c6eb68"><code>918180d</code></a> <code>Move Git and Pre-releases sections to separate doc</code></li> </ul> <p>See the <a href="https://urls.greenkeeper.io/release-it/release-it/compare/f800a703c28a240435ad0d738f16d82922ec3d35...f513d22197e42f25cb6cde6b8519937a65bb6513">full diff</a></p> </details>


<details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>


Your Greenkeeper bot :palm_tree:

+1 -1

1 comment

1 changed file

greenkeeper[bot]

pr closed time in 21 days

issue commentTeamOverVue/OverVue

Error Unknown command "dev"

image

ulivz

comment created time in 21 days

issue commentTeamOverVue/OverVue

Error Unknown command "dev"

?

ulivz

comment created time in 22 days

push eventulivz/poi

snyk-test

commit sha 70d1f21e652e3e985cc8db65cfc61a2885cf0003

fix: packages/poi-preset-elm/package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-LODASH-450202

view details

push time in 23 days

create barnchulivz/poi

branch : snyk-fix-36765f8accf8faa89bb1f702700dffde

created branch time in 23 days

startedwebpack/loader-runner

started time in 24 days

PR opened vuejs/vuepress

feat: markdown.extractHeaders option

<!-- Please don't delete this template -->

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

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:
module.exports = {
  markdown: {
    extractHeaders: ['h2', 'h3', 'h4'] // defaults to ['h2', 'h3'] 
  }
}

Replacement of #1111

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:

  • [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], 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:

+23 -6

0 comment

5 changed files

pr created time in 25 days

create barnchsherry/vuepress

branch : refactor/extract-headers-implementation

created branch time in 25 days

push eventulivz/timeout-wrap

greenkeeper[bot]

commit sha 0ce03210ad5c39d9742a1b067b74f65661f47457

Update dependencies to enable Greenkeeper 🌴 (#1) * chore(package): update dependencies * docs(readme): add Greenkeeper badge

view details

push time in 25 days

PR merged ulivz/timeout-wrap

Update dependencies to enable Greenkeeper 🌴 greenkeeper

Let’s get started with automated dependency management for timeout-wrap :muscle:

🔒 Greenkeeper has found a yarn.lock file in this repository. Greenkeeper supports lockfile updates for public packages. If you use private packages in your repository, please use greenkeeper-lockfile to make sure these can get updated as well.

This pull request updates all your dependencies to their latest version. Having them all up to date really is the best starting point for keeping up with new releases. Greenkeeper will look out for further dependency updates and make sure to handle them in isolation and in real-time, but only after you merge this pull request.

Important: Greenkeeper will only start watching this repository’s dependency updates after you merge this initial pull request.


<details> <summary>🏷 How to check the status of this repository</summary>

Greenkeeper adds a badge to your README which indicates the status of this repository.

This is what your badge looks like right now :point_right: Greenkeeper badge </details> <details> <summary>🙈 How to ignore certain dependencies</summary>

You may have good reasons for not wanting to update to a certain dependency right now. In this case, you can change the dependency’s version string in the package.json file back to whatever you prefer.

To make sure Greenkeeper doesn’t nag you again on the next update, add a greenkeeper.ignore field to your package.json, containing a list of dependencies you don’t want to update.

// package.json
{
  …
  "greenkeeper": {
    "ignore": [
      "package-names",
      "you-want-me-to-ignore"
    ]
  }
}

</details> <details> <summary>👩‍💻 How to update this pull request</summary>

  # Change into your repository’s directory
  git fetch --all
  git checkout greenkeeper/initial
  npm install-test
  # Adapt your code until everything works again
  git commit -m 'chore: adapt code to updated dependencies'
  git push https://github.com/ulivz/timeout-wrap.git greenkeeper/initial

</details> <details> <summary>✨ How do dependency updates work with Greenkeeper?</summary>

After you merge this pull request, Greenkeeper will create a new branch whenever a dependency is updated, with the new version applied. The branch creation should trigger your testing services and check whether your code still works with the new dependency version. Depending on the the results of these tests Greenkeeper will try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date.

-  "underscore": "^1.6.0"
+  "underscore": "^1.7.0"

The above example shows an in-range update. 1.7.0 is included in the old ^1.6.0 range, because of the caret ^ character . When the test services report success Greenkeeper will silently delete the branch again, because no action needs to be taken – everything is fine.

However, should the tests fail, Greenkeeper will create an issue to inform you about the problem immediately.

This way, you’ll never be surprised by a dependency breaking your code. As long as everything still works, Greenkeeper will stay out of your way, and as soon as something goes wrong, you’ll be the first to know.

-  "lodash": "^3.0.0"
+  "lodash": "^4.0.0"

In this example, the new version 4.0.0 is not included in the old ^3.0.0 range. For version updates like these – let’s call them “out of range” updates – you’ll receive a pull request.

This means that you no longer need to check for new versions manually – Greenkeeper will keep you up to date automatically.

These pull requests not only serve as reminders to update: If you have solid tests and good coverage, and the pull requests passes those tests, you can very likely just merge it and release a new version of your software straight away :shipit:

To get a better idea of which ranges apply to which releases, check out the extremely useful semver calculator provided by npm. </details> <details> <summary>FAQ and help</summary>

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper. </details>


Good luck with your project and see you soon :sparkles:

Your Greenkeeper bot :palm_tree:

+5 -5

0 comment

2 changed files

greenkeeper[bot]

pr closed time in 25 days

create barnchulivz/vuepress-theme-blog

branch : feat/wip-branch

created branch time in a month

push eventulivz/awesome-vuepress

ULIVZ

commit sha 83ca7a84e4f73517bc3dd176dc12fa08d400cf45

workflow: add stale bot config

view details

push time in a month

push eventulivz/awesome-vuepress

ULIVZ

commit sha 3364f1c4cb34f3c3239334c2ec683c8d34c0ea5d

feat: add vuepress-plugin-check-md

view details

push time in a month

push eventulivz/vuepress-plugin-check-md

ULIVZ

commit sha 182936b7138397f31ec537e49a5ed093028a64c1

0.0.1

view details

ULIVZ

commit sha e88241bbe14f06ef051e54f744359a5f4f5e4fc0

Merge branch 'master' of https://github.com/ulivz/vuepress-plugin-check-md

view details

ULIVZ

commit sha dcac0425cef95e99fcad19ae92822f67d1b87958

chore: bump check-md

view details

ULIVZ

commit sha a8601505b7e1e99f45f517727549019c51dcf377

0.0.2

view details

push time in a month

push eventulivz/vuepress-plugin-check-md

ULIVZ

commit sha 60fda9235c600d27028b2d0081bfdb5d179c989c

chore: readme

view details

push time in a month

startedulivz/vuepress-plugin-check-md

started time in a month

push eventulivz/vuepress-plugin-check-md

ULIVZ

commit sha 5d3be215c569ea16dcecd630361257ea669209db

feat: init

view details

push time in a month

push eventulivz/check-md

ULIVZ

commit sha 8cdb0cbb18a134b209c17d4d687739d11a1933e8

feat: allow to custom slugify function

view details

push time in a month

create barnchulivz/check-md

branch : feat/support-custom-slugify

created branch time in a month

fork ulivz/check-md

checks dead links of markdown

fork in a month

push eventulivz/vuepress-plugin-check-md

ULIVZ

commit sha f43ffc312cf769eea28d7667f2bc300f5e36729d

feat: init

view details

push time in a month

push eventulivz/vuepress-plugin-check-md

ULIVZ

commit sha bf663fbff92dc6ab22d8b5f1644b04f27d1e8a08

feat: init

view details

push time in a month

push eventulivz/vuepress-plugin-check-md

ULIVZ

commit sha 626aaf1fb889aabfa24118678c0c61c0a582aaf4

feat: init

view details

push time in a month

push eventulivz/vuepress-plugin-check-md

ULIVZ

commit sha d8adb99a4f95bc27f89fdfe9e47214d09d88bfec

feat: init

view details

push time in a month

push eventulivz/vuepress-plugin-check-md

ULIVZ

commit sha 4d9cbfd4f7fd81c64c3e9fa8c679f1235804a114

feat: init

view details

push time in a month

create barnchulivz/vuepress-plugin-check-md

branch : master

created branch time in a month

created repositoryulivz/vuepress-plugin-check-md

vuepress check-md - checks dead links of markdown.

created time in a month

more