Skip to content

Conversation

@JoelEinbinder
Copy link
Contributor

npm is ok

Copy link
Contributor

@aslushnikov aslushnikov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Joel!

- "export DISPLAY=:99.0"
- "sh -e /etc/init.d/xvfb start"
install:
- yarn install
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

curious: why isn't the npm install step necessary any longer?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was never necessary, but I finally read the docs.

*.swp
*.pyc
.vscode
package-lock.json
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dont' you want to check in the package-lock.json now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope. With developers using separate package managers, the locks would often be ignored. Checking in the lock files proved more of a headache than security it gives over our dev-dependencies.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@paulirish package-lock.json is ignored on the npm install puppeteer step; on the trybots, we'd like to install the same way our users do.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

k sg!

Copy link
Contributor

@ebidel ebidel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine. Why do we not like yarn though?

@aslushnikov
Copy link
Contributor

Why do we not like yarn though?

@ebidel yarn is great, but there's some confusion on npm vs yarn usage in the docs: #1799.

We picked NPM since that's what dev team uses on a daily basis.

@aslushnikov aslushnikov merged commit f2b6016 into puppeteer:master Jan 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants