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

Consider adding @bigtest/interactor to package.json on bigtest init #32

Open
cowboyd opened this issue Sep 28, 2018 · 1 comment
Open
Labels

Comments

@cowboyd
Copy link
Contributor

cowboyd commented Sep 28, 2018

As part of writing the guides, @SamKeathley put in a step to install the @bigtest/interactor package. This seems like a slam dunk for something that we should be doing automatically. I mean, if yiou aren't using interactor, then why are you using BigTest?

https://github.com/bigtestjs/bigtestjs.io/blob/81442cce44dba5fc454db42f32b2d594a77d21c5/source/guides/getting-started/quick-start.html.md

Questions

Should it use yarn? Maybe if it detects a yarn executable in the path and ayarn.lock. Otherwise, maybe we can have a --yarn option to use yarn even in the event that there was not a yarn.lock. Although a yarn executable would need to be in the path.

@Robdel12
Copy link
Contributor

Yeah we'll totally do this. And if there's both in the project prompt for npm or yarn.

@taras taras transferred this issue from bigtestjs/cli Dec 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants