-
Notifications
You must be signed in to change notification settings - Fork 41
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
npm package broken #99
Comments
The same here. |
It is not just the npm package. Building from source gives me the same. But the problem happens only because you don't have a structured blacksmith directory (with content, layouts and the .blacksmith file). |
+1 |
I get the same error message, are there no development done in this project? According to the documentation this project would have suited my documentation needs but I can't get it to run? Any recommendations on what to use instead with a similar feature set? |
@DanielSundberg This is abandoned, but perhaps you will find what you want in these forks. |
Likewise. Rendering: blacksmithy
Error rendering: blacksmithy
{ [Error: ENOENT, open 'blacksmithy/.blacksmith'] errno: -2, code: 'ENOENT', path: 'blacksmithy/.blacksmith' }
[ 'Error: ENOENT, open \'blacksmithy/.blacksmith\'',
' at Error (native)' ] Will check the forks. |
I installed blacksmith as described:
$ sudo npm install blacksmith -g
However when I run it I get errors:
The text was updated successfully, but these errors were encountered: