search

componentjs / component

frontend package manager and build tool for modular web applications
https://github.com/componentjs/guide
MIT License
4.55k stars 305 forks source link

Getting started doesn't start #560

Closed dandv closed 10 years ago

dandv commented 10 years ago

component build returns

error : failed to lookup "getting-started-with-component"'s dependency "necolas-normalize.css"

With the component.json from getting started:

{
  "name": "getting-started-with-component",
  "dependencies": {
    "necolas/normalize.css": "^3.0.0"
  }
}

component install shows this:

     install : necolas/normalize.css@^3.0.0                                                                         
   error : failed to fetch https://raw.githubusercontent.com/necolas/normalize.css/^3.0.0/component.json, got 404 "Not Found"
dandv commented 10 years ago

If I replace "necolas/normalize.css": "^3.0.0" with "necolas/normalize.css": "*", component build still fails, unless it's run after component install.

I'm going through the Get Started in the shoes of a Component n00b, so things should run right out of the box.

jonathanong commented 10 years ago

you probably need to upgrade component

dandv commented 10 years ago

I had just installed 0.19.9 fresh.

wryk commented 10 years ago

You should use 1.x for semver support

dandv commented 10 years ago

sudo npm installl -g component brings 0.19.9. That's what new users will run, right?

vendethiel commented 10 years ago

not really

kenany commented 10 years ago

It is unless they do

$ npm install -g component@1.0.0-rc5
dandv commented 10 years ago

Same issue reported by another user at https://github.com/component/guide/issues/16

jonathanong commented 10 years ago

you know what... i think what the problem is is that 0.19.9 was release last, and latest defaults to the latest by date, not by version. ugh stupid npm

vendethiel commented 10 years ago

not sure if npm should install RCs though :/ maybe when they're major, hard to tell

gnimmelf commented 10 years ago

Bump. npm update component gave 0.19.9 and nothing gets buildt.

pirxpilot commented 10 years ago

yup - npm 'latest' means 'chronologically latest' - see: npm/npm#3397 maybe for now we should tell people to install 1.x like this:

npm install component@1
timaschew commented 10 years ago

or to publish component 0.x with a different tag: npm publish --tag=0.19 this remains the latest tag, which is default and would be overwritten otherwise

netpoetica commented 10 years ago

@timaschew I think release of 1.0 will close this issue no?

timaschew commented 10 years ago

Yes ;)

timaschew commented 10 years ago

fixed since rc-6 release

netpoetica commented 10 years ago

Just confirmed this as well, looks good