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

questions: isn't it annoying to touch so many files if upgrading a remote dependency? #927

Closed
timaschew opened this issue Jun 13, 2015 · 7 comments

Comments

@timaschew
Copy link

for instance: if you want to upgrade component/dom you need to touch 24 files:

https://github.com/DemocracyOS/app/search?p=2&q=component%2Fdom&utf8=%E2%9C%93

@gvilarino
Copy link
Member

@timaschew yeah, that's one of the problem's we've faced with component, as well as hitting the github API rate-limit way too often.

We've been exploring with browserfify as a solution for the frontend build recently and we're probably adopting it as a definite solution for this. We love the component approach to modularization, but the absence of a registry and depending entirely on the github API dosn't scale for mid-to-large project like ours :/

@timaschew
Copy link
Author

as well as hitting the github API rate-limit way too often.

even if you use a token?

but the absence of a registry and depending entirely on the github API dosn't scale for mid-to-large project like ours :/

yes, totally agree. There are also some other drawbacks.

Currently I'm experimenting with jspm. It is really awesome, it's like component also a package manager and support github and npm.
Just now I setup a configuration in jspm to support component styled directory structures and require paths, so it's working without touching the code!
I will write a blog article and maybe a small tool to convert component apps into jspm.

R.I.P component

@gvilarino
Copy link
Member

even if you use a token?

Yeah, even with a token, 2 out of 3 (clean) builds would fail. For new instances, we would usually have to push 2-4 times to heroku to get a working deployment.

We'll definitely check jspm out. Is there any repo/gist you'd recommend us checking out?

I will write a blog article and maybe a small tool to convert component apps into jspm.

Looking forward to it!

R.I.P component

:(

@timaschew
Copy link
Author

https://github.com/jspm/demo-es6
https://github.com/guybedford/jspm-demo
Am 14.06.2015 17:00 schrieb "Guido Vilariño" [email protected]:

even if you use a token?

Yeah, even with a token, 2 out of 3 (clean) builds would fail. For new
instances, we would usually have to push 2-4 times to heroku to get a
working deployment.

We'll definitely check jspm out. Is there any repo/gist you'd recommend
us checking out?

I will write a blog article and maybe a small tool to convert component
apps into jspm.

Looking forward to it!

R.I.P component
:(


Reply to this email directly or view it on GitHub
#927 (comment).

@gvilarino
Copy link
Member

Thanks!

@timaschew
Copy link
Author

turns out webpack has a better and more configurable API.

see componentjs/component#639

@gvilarino
Copy link
Member

👍

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

No branches or pull requests

2 participants