These are chat archives for Email-builder/email-builder-core

18th
Apr 2015
Steven Miller
@yargalot
Apr 18 2015 02:08
I'll knock the grunt email builder over to the org
Steven Miller
@yargalot
Apr 18 2015 02:24
Le done
Jeremy Peter
@jeremypeter
Apr 18 2015 05:02
Le Awesome!
Jeremy Peter
@jeremypeter
Apr 18 2015 05:57
Do you think we should transfer the Email-Builder repo to the grunt-email-builder repo?
Steven Miller
@yargalot
Apr 18 2015 06:01
Naming is more obvious, just wondering about republishing it to npm
Would we lost the history?
*lose
Jeremy Peter
@jeremypeter
Apr 18 2015 06:31
No I don't think so, we would just need to change the repo/issues props in the package.json. NPM I believe keeps track of the module name and versions combined. So if we were to deprecate the module and someone else tried to make a new grunt-email-builder at version 2.0.0. They wouldn't be able to, they would have to use a version that was never used.
This is what npm says:
blockquote Even if a package version is unpublished, that specific name and version combination can never be reused. In order to publish the package again, a new version number must be used.
Steven Miller
@yargalot
Apr 18 2015 06:34
So we should publish it at 3.0 if we move the repo
Makes sense
Would either be that or rename the existing repo
But yeh should def make it grunt-email-builder
Makes sense if we make a gulp or broccoli or whatever kinda version
Can just put the core into the existing codebae
Jeremy Peter
@jeremypeter
Apr 18 2015 06:37
Oh true, I guess we could just rename it the git repo. I did create a feature branch that's using email-builder-core that I didn't push yet
has more tests and a lot less code
Steven Miller
@yargalot
Apr 18 2015 06:38
Copy paste job into the existing repo?
More tests less code is awesome
Depends what's easier I guess
Never had to do this before =p
Jeremy Peter
@jeremypeter
Apr 18 2015 06:42
Yeah neither have I hahah. I can just copy and paste. I can look into renaming the Email-Builder repo and changing up the package.json
sound good? Unless you already know how
Steven Miller
@yargalot
Apr 18 2015 06:43
Let's give that a while
*whirl
You have complete access to the repo now! ;D
Unless you can push a branch to another repo lol
Jeremy Peter
@jeremypeter
Apr 18 2015 06:45
Sweetness, let's pray I don't break everything lol. Yeah at this point, I feel safer copy and pasting everything
Steven Miller
@yargalot
Apr 18 2015 06:45
Awesomesauce lol
Pretty sure it'll be fine lol
Unsure about the travis stuff lol
Jeremy Peter
@jeremypeter
Apr 18 2015 07:07
Going smooth so far, I didn't have to copy and paste after all. I just had to point my local to the new remote url using:
git remote set-url origin https://github.com/Email-builder/grunt-email-builder.git