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

feat(playroom): Add Playroom support #367

Merged
merged 12 commits into from May 28, 2019
Merged

feat(playroom): Add Playroom support #367

merged 12 commits into from May 28, 2019

Conversation

markdalgleish
Copy link
Member

This PR adds Playroom support via the sku playroom and sku build-playroom commands.

@markdalgleish markdalgleish requested a review from a team as a code owner May 28, 2019 07:05
@markdalgleish markdalgleish changed the title feat(playroom): Add Playroom feat(playroom): Add Playroom support May 28, 2019
Copy link
Contributor

@mattcompiles mattcompiles left a comment

Choose a reason for hiding this comment

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

Can we regen the yarn.lock completely? Seems like it's in a strange state with some dependencies.

@@ -1,5 +1,6 @@
const supportedBrowsers = require('browserslist-config-seek');
const path = require('path');
const isTypeScript = require('../lib/isTypeScript');
Copy link
Contributor

Choose a reason for hiding this comment

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

isTypeScript is actually a function. However, it probably should be a value because otherwise, we may call it multiple times and it's not zero cost.

@michaeltaranto michaeltaranto merged commit 20b1479 into master May 28, 2019
@michaeltaranto michaeltaranto deleted the playroom branch May 28, 2019 23:54
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.

None yet

3 participants