Fix Yarn failure + other updates #109
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ember CLI detects the yarn.lock file to decide whether to use Yarn or not. Pending yarnpkg/yarn#5059, we should switch to npm by default.
This package has a dependency on node-sass, which means creating a new app takes a really long time while it compiles libsass. This is a poor first impression for us to make, especially because we hide the fact that it's libsass compiling.
This version fixes some compatibility issues with TypeScript
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
yarn.lockfile so app creation doesn't fail out of the gate.@glimmer/application-pipelineto 0.10.^operator in package.json with a~because TypeScript doesn't follow SemVer.ember-cli-sassby default.(Originally submitted as glimmerjs/glimmer-blueprint#79.)