Docpad Run + Twitter Bootstrap = npm ERR! Darwin 13.4.0 #894
Comments
|
Just a note. Two more executions of |
|
Interesting, noted. |
|
Docpad Run + HTML5 Boilerplate seems to be out of date, too. > js2coffee@0.2.7 preinstall /Users/main/Projects/fun/docpad/awesome/node_modules/docpad/node_modules/cson/node_modules/js2coffee
> npm run-script ./cyclic.js
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "run-script" "./cyclic.js"
npm ERR! node v0.10.33
npm ERR! npm v2.1.8
npm ERR! missing script: ./cyclic.js
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /Users/main/Projects/fun/docpad/awesome/node_modules/docpad/node_modules/cson/node_modules/js2coffee/npm-debug.log
> ambi@2.2.0 preinstall /Users/main/Projects/fun/docpad/awesome/node_modules/docpad/node_modules/safeps/node_modules/taskgroup/node_modules/ambi
> node ./cyclic.js
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.10.33
npm ERR! npm v2.1.8
npm ERR! code ETARGET
npm ERR! notarget No compatible version found: eco@'>=1.1.0 <1.2.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["1.0.0","1.0.1","1.0.2","1.0.3","1.1.0-rc-1","1.1.0-rc-2","1.1.0-rc-3"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/main/Projects/fun/docpad/awesome/npm-debug.log
error: Something went wrong with the action
error: An error occured:
Error: npm WARN deprecated extendable@0.0.6: This project has been renamed to extendible. This project will not receive any updates anymore
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "run-script" "./cyclic.js"
npm ERR! node v0.10.33
npm ERR! npm v2.1.8
npm ERR! missing script: ./cyclic.js
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /Users/main/Projects/fun/docpad/awesome/node_modules/docpad/node_modules/cson/node_modules/js2coffee/npm-debug.log
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.10.33
npm ERR! npm v2.1.8
npm ERR! code ETARGET
npm ERR! notarget No compatible version found: eco@'>=1.1.0 <1.2.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["1.0.0","1.0.1","1.0.2","1.0.3","1.1.0-rc-1","1.1.0-rc-2","1.1.0-rc-3"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/main/Projects/fun/docpad/awesome/npm-debug.log
at ChildProcess.<anonymous> (/usr/local/lib/node_modules/docpad/node_modules/safeps/out/lib/safeps.js:165:23)
at ChildProcess.emit (events.js:98:17)
at maybeClose (child_process.js:756:16)
at Socket.<anonymous> (child_process.js:969:11)
at Socket.emit (events.js:95:17)
at Pipe.close (net.js:465:12) |
|
Yeah. Most if not all of the skeletons are out of date usually. I suggest just not using them at all. They are more trouble than they are worth, usually. If you want you can use them as reference though. Their source code can have some valuable stuff... |
|
Consider removing skeletons from docpad or just from documentation and cli interface. They are never used by pro users and most f time it is the first thing to try when you are newbie and boom errors. DocPad is pretty stable and well working but the community is unable to keep up with the skeletons and they are causing more harm than benefit. |
|
@dimitarkolev I have considered removing them from the docs. They also have to be removed from the code and npm though, and that's up to @balupton. |
|
Maybe we should just have an |
|
That could work as well. Although then we have to make it clear that if it says it's outdated we won't offer support for them since they can cause a ton of problems, therein wasting a lot of time. |
|
I believe removing them from the CLI interface is much better than putting
|
|
Indicating they're outdated, can perhaps make people maintain them. Right now the issue is with people believing they are up to date, and them breaking. |
|
Its worth trying for some time 6 months for example and see if it works.
|
|
True. Removing them as options from the CLI would be a quick fix. |
|
I agree. That would also mean that if a user actually wants the skeleton then he will employ some techniques that a beginner user may not know. So he knows what he's getting into. |
|
I constantly follow the open issues and can not understand any of the @balupton 's reasoning for keeping skeletons part of docpad CLI and its documentation. Almost every recent issue reported here is because of broken skeleton. |
|
I mean skeletons are great. But the fact that the dependencies aren't stable (for some reason) is what breaks them so much. Although in the end you do always benefit from developing a website from zero instead of using a skeleton... |
|
Many established MVCs have skeletons though and it's part of the reason why developers choose to build off of existing MVCs. Otherwise it would be like 2004 when we all made our own everythings. No one wants to go back to that. |
|
Right. But I think skeletons should be used as reference. Especially considering that right now it's causing way more problems than it's worth, IMO. |
|
Oh yeah. As of right now the skels are only being used as reference for me personally. But later it should be noted that skeletons are an important priority for vetted MVCs. |
|
Can we proceed with #894 (comment) and be done with this. |
|
This is a terrible out-of-the-box experience:
Please, strip the skeletons out if the team and community can't or won't maintain them. |
|
@garthk +1 |
|
@garthk is you find a broken skeleton, send a pull request on https://github.com/docpad/extras/blob/docpad-6.x/exchange.json to add |
|
Should any distinction be made between outdated but working and outdated, fully not working skeletons? I agree this is a pretty bad experience, since after working through npm permissions issues I finally get to the point of trying to get a site started and I choose a skeleton that fails during rendering. Since I already had issues I start thinking it's my fault, maybe I installed Docpad wrong. On the other hand I do think it's useful, so maybe cut down on the amount of skeletons available and keep a few as officially maintained that are presented to the user during install? For reference, I tried three and one worked. If I get an answer to my first question I can put in a pull request for these.
|
|
Let me tell you my impressions of docpad:
|
|
Closing due to age. Ecosystem has likely fixed this. Try again with v6.80 or later. |
Full command log below:
Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: