Skip to content
This repository was archived by the owner on May 13, 2024. It is now read-only.

Conversation

KaptenJansson
Copy link
Contributor

@fippo PTAL

@KaptenJansson
Copy link
Contributor Author

Travis will run after this PR.

@fippo
Copy link
Contributor

fippo commented Jan 26, 2016

that allows us to just require('whatever-we-call-this-on-npm/src/selenium/selenium-lib') right? Any way way can get rid of the path? Maybe by having an index.js that requires src/selenium/selenium lib and exports this as module.exports.selenium?

LGTM otherwise

@KaptenJansson
Copy link
Contributor Author

Re for the require question: Yes.

Yeah the path is a bit long but I foresee adding more stuff in here, having a main.js file which can control what's being exposed etc is a good idea. Will add that.

KaptenJansson added a commit that referenced this pull request Jan 28, 2016
Add grunt, package info etc
@KaptenJansson KaptenJansson merged commit 2c4a34a into master Jan 28, 2016
@KaptenJansson KaptenJansson deleted the addBarebones branch February 9, 2016 15:42
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.

2 participants