Repo: https://github.com/Phenomen/ose
Deployed version (with bugged anchor links): https://ose.phenomen.now.sh/classic-fantasy/
Anchor link is #褌械褉屑懈薪芯谢芯谐懈褟
Anchor link is: #褌械褉屑懈薪芯n芯谐懈褟
Cyrillic "谢" is replaced by Latin "n" in the anchor link.
Zeit is used for build and deploy. Result is the same as on local machine.
npx vuepress info in my VuePress project:Related: https://github.com/kentcdodds/match-sorter/issues/57
Their solution is to replace diacritics with remove-accents instead.
Do you think you can work on it ? We are using remove accents actually maybe bad configs
@f3ltron I would like to try
top @larionov ! Dont hesitate to ask me if you need some help about understanding part of vuepress
fork the project
create a branche
create the pr and reference to this issue :)
@f3ltron Can you help me please?
I'm having trouble running tests locally, even on HEAD I get a bunch of tests are failing.
I do:
yarn
yarn bootstrap
yarn build
yarn test
and I get this: https://gist.github.com/larionov/5e052b1de000297f6d14743a1baee327
Also just removing one dependency from shared-utils changes yarn.lock file considerably, updating a lot of dependencies and CONTRIBUTING.md seems to be outdated, there is no yarn clean command.
i will have a look on it. I am a bit busy but i will have a look this weekend.
You are running tests on master branch ?
i tried myself locally
yarn bootstrap (it will do yarn tsc and install in every project)
yarn test
@f3ltron sorry, figured it out, realized that I had a very old fork of vuepress.
Please see the PR. https://github.com/vuejs/vuepress/pull/1855
For some reason it is not mentioned in the issue, what did I do wrong?
Dont be sorry it's ok we all work together ! 馃挴
just start to pull master into your fork.
yarn boostrap
yarn test and it should work
Tell me more about what u doing now.
I did the fix, opened the PR #1855 and waiting for the comments on it
This error has affected me too, can you please see please
I have the same problem. How is progress?
I will try to resolve the conflicts today
Resolved
Most helpful comment
This error has affected me too, can you please see please