We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm trying to employ Styledown for the first time and have had good results using v1.02 and specifying markdown files plus a markdown config file:
styledown components/a/example.md components/b/example.md styledownConf.md > docs/styleguide.html
When I tried to go for the wildcard: styledown components/*.md styledownConf.md > docs/styleguide.html I received the following error:
styledown components/*.md styledownConf.md > docs/styleguide.html
ENOENT: no such file or directory
The documentation shows the use of a wildcard character for both scss and md, so I'm curious if anyone has insights on this.
The text was updated successfully, but these errors were encountered:
I had this issue as well. I was using
styledown dist/styleguide/styles/*.css config/config.md > public/styleguides.html
The problem ended up being that the 'public' directory had not been created. Once I created it then the command worked just fine.
Sorry, something went wrong.
No branches or pull requests
I'm trying to employ Styledown for the first time and have had good results using v1.02 and specifying markdown files plus a markdown config file:
styledown components/a/example.md components/b/example.md styledownConf.md > docs/styleguide.html
When I tried to go for the wildcard:
styledown components/*.md styledownConf.md > docs/styleguide.html
I received the following error:ENOENT: no such file or directory
The documentation shows the use of a wildcard character for both scss and md, so I'm curious if anyone has insights on this.
The text was updated successfully, but these errors were encountered: