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

add the repository field in order to avoid the new npm v1.2.20 warning #2

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

trjh
Copy link

@trjh trjh commented Aug 16, 2013

"npm WARN package.json [email protected] No repository field."

(bit trivial, but had me briefly confused)

npm WARN package.json [email protected] No repository field.

(bit trivial, but had me briefly confused)
- skip heroku login and .env copy steps, as my build takes care of that
- skip ssh key bits, as i use ssh -A from my laptop

index.html changes:
- add my own button code (instead of class one)
- use my own google analytics tags (though i seem to have forgot one of them)

web.js change:
- add some code used during exploration of this module, and javascript.  shows
  me how objects/variables work, demonstrated my suspicion that .env wasn't
  automagically passed to heroku (i missed the config:push bit in the
  instructions), played a bit with JSON parsing, and a simple
  dev-vs-production trigger
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.

1 participant