-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vuepress project cannot be in some folder name start with n #642
Labels
Comments
Thanks for your reporting, but I don't have windows computer, it there anyone could help me to sync with it? |
@ulivz quick solution: const overridePath = path
.resolve(sourceDir, '.vuepress/override.styl')
.replace(/[\\]+/g, '/') and also: const stylePath = path
.resolve(sourceDir, '.vuepress/style.styl')
.replace(/[\\]+/g, '/') Like that normalize-path |
Thanks to notiv-nt & ulivz, problem solved. Are you going to release this bug fix? |
ulivz
added
contribution welcome
Contributions welcome
type: enhancement
Request to enhance an existing feature
and removed
help wanted
Extra attention is needed
labels
Jul 31, 2018
18 tasks
ulivz
pushed a commit
that referenced
this issue
Aug 1, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug report
Version
0.11.0
Steps to reproduce
(undefined) ./node_modules/vuepress/lib/app/.temp/override.styl
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/stylus-loader/index.js):
Error: C:\new\mydoc\web\node_modules\vuepress\lib\app.temp\override.styl:1:74
1| @import("C:\new\mydoc\docs\.vuepress\override.styl")
-------------------------------------------------------------------------------^
failed to locate @import file C:
ew\mydoc\web\docs\.vuepress\override.styl
What is expected?
"npm run docs:build" should build in any folder name
What is actually happening?
"npm run docs:build" building failed if the folder name start with "n"
Other relevant information
The text was updated successfully, but these errors were encountered: