Skip to content
This repository has been archived by the owner on May 19, 2020. It is now read-only.

Merge dependencies and devDependencies #297

Merged
merged 2 commits into from
May 31, 2016
Merged

Conversation

jeremiak
Copy link
Contributor

To close #285, I have merged the two sections of the package.json file and regenerated the npm-shrinkwrap.json.

From the issue:

In order for the deck development team to always know what version of every dependency is being used in the app AND for the deck development team to have a simpler understanding of dependencies, all dev dependencies should be considered dependencies.

Jeremia Kimelman added 2 commits May 31, 2016 12:10
To close #285, I have merged the two sections of the `package.json`
file and regenerated the `npm-shrinkwrap.json`.

I did this because it is important that the deck development team
always know what version of every dependency is being used in the app
AND for the deck development team to have a simpler understanding of
dependencies.
We are no longer using `less` and in the process of merging
dependencies into devDependencies I realized we should also do some
cleanup
@coveralls
Copy link

coveralls commented May 31, 2016

Coverage Status

Coverage remained the same at 72.599% when pulling 985fc54 on jk-merge-dev-deps into ffb4003 on staging-alpha.

@msecret msecret merged commit a93df3e into staging-alpha May 31, 2016
@jeremiak jeremiak deleted the jk-merge-dev-deps branch June 2, 2016 20:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants