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

Shift dependencies to devDependencies. #1764

Merged
merged 1 commit into from
Jan 31, 2017
Merged

Conversation

bnjmnt4n
Copy link
Collaborator

@bnjmnt4n bnjmnt4n commented Dec 8, 2016

The reveal.js npm module is typically installed to access the CSS/JS assets for Reveal.js. For those that want to run the plugins, they would clone the whole repository. Hence, it doesn’t make sense to include those as dependencies, which will increase download times.

Closes #1734.

Note: this might count as a breaking change.

The `reveal.js` npm module is typically installed to access the CSS/JS
assets for Reveal.js. For those that want to run the plugins, they would
clone the whole repository. Hence, it doesn’t make sense to include
those as `dependencies`, which will increase download times.

Closes hakimel#1734.
@Nava2
Copy link

Nava2 commented Jan 4, 2017

I've been trying to use reveal.js with webpack, and to install via npm it brings in a lot of different build tools that I don't want. This would be excellent to get put in place.

E: Additionally, it looks like head.js is not included in the NPM module. Meaning, it's not installed and can't be imported as a module.

@hakimel hakimel merged commit 581da02 into hakimel:dev Jan 31, 2017
@hakimel
Copy link
Owner

hakimel commented Jan 31, 2017

🙌

@Nava2
Copy link

Nava2 commented Jan 31, 2017

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants