Advertisement
Guest User

Untitled

a guest
Feb 22nd, 2017
76
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.84 KB | None | 0 0
  1. 1.) `npm i -D webpack-defaults`
  2.  
  3. 2.) Add `webpack-defualts` to scripts
  4.  
  5. 3.) Execute `npm run webpack-defaults`
  6.  
  7.  
  8. Initial update checkpoint
  9. - Babel outputs to `./dist` the `files` field for an existing repo is all but guaranteed to be wrong and require updating. This should be documented unless there is a way to migrate existing files settings to incorporate the `dist` output ( more trouble than it's worth imo)
  10. - Uses yarn, `yarn-debug.log*` needs to be ingored on update as well.
  11. - travis.yml `before_script` & `script` are duplicating commands for npm & yarn. In Travis we should only use yarn.
  12. - Are we outputing a `README.md` from the approved template on an empty repo? Should we spit out a `README_TMPL.md` to assist people in upgrading their existing readme to the contrib standard?
  13.  
  14. Everything else looks good as it relates to initial command execution.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement