Skip to content
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

use component-name for npm #67

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

use component-name for npm #67

wants to merge 1 commit into from

Conversation

timaschew
Copy link
Member

allow to use require('component-model') on server and client

//edit
and use semantic versioning via npm

@vendethiel
Copy link
Member

that sounds like a hack. Maybe a clever one, but still a hack...

@timaschew
Copy link
Member Author

Or maybe best-practice https://github.com/componentjs/guide/blob/master/creating-components/best-practices.md#publishing-to-npm

You don't need to use require('component-model') on the client, you can still write require('model') but on the server you maybe want to use npm with semver. This is currently not possible because it's not published on npm, so npm install component/model and require('model') is not a solution

@timaschew
Copy link
Member Author

several packages have this style: https://gist.github.com/timaschew/eeed4056b16b14f2dccf
so, is this a hack or a convention?

@19h
Copy link

19h commented Feb 23, 2015

👍 for this "hack". It's far cleaner to use.

@vendethiel
Copy link
Member

Alright, I'm okay with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants