bump version, so it can be used with component again

[component]

bump version, so it can be used with component again

[jonathanong]

@defunctzombie @TooTallNate browserify masters, how to best handle this? are we still doing try/catch's?

[TooTallNate]

Well my solution is add-component-symlinks, to fix the npm vs. component "require" name discrepancy.

The try/catches must not be in place in order to work with browserify.

[defunctzombie]

The following setup should work with node, browserify, and component.

Assume package.json is published as foobar-component and component.json is foobar

try {
   var module = require('foobar-component');
}
catch() {
   var module = require('foobar');
}

Package.json needs to have the following

"browser": {
    "foobar": "foobar-component"
}

This will allow browserify to not bork on the foobar require (since it tries to resolve at build time). And it will allow node to work because it will find foobar-component via normal node_modules lookup.

If you don't need to support node and just want to support component and browserify, the js is simpler.

var module = require('foobar');

Hope that helps clear up how to support all three environments.

[TooTallNate]

Huh... hacky, but clever. I wish there was a way to avoid all the try/catching in the actual script file though :( (ya, I like when they work in node as well. all 3)

[rauchg]

Having try/catch all over the place is really painful :(

[jonathanong]

changed it to component-type :D 0.2.1 it's also component-clone now.

[ntharim]

require('component-type') doesn't work for me using component. Why is that?

[jonathanong]

gah it doens't work? is the current builder broken?

[ntharim]

doesn't work with 0.10.x. I haven't tried 0.12.0 or builder2 so I don't know about those ones.

[jonathanong]

k i'll change it

[jonathanong]

man but i don't want to. all the solutions are ugly

[defunctzombie]

this is what happens when you create two package managers and one of them doesn't have namespaces.

Reality.

[lvivier]

+1 to reality, I got bit by this today (also [email protected]) :(

[jonathanong]

k pushed again -___-