You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
I would think that there would be no changes needed in our code, when the package manager is changed. As I understand, yarn still works on npm-"backend"? There is no more information printed and I don't know what to do, because I have no deeper knowledge of how yarn is working with it's cached dependencies, because I'm "only" a angular(5) developer who is using yarn for package management.
What would be the way to proceed? I've switched from npm to yarn, because sometimes uncontrollable errors appeared when npm re-installs were done.. but the dependencies were correct when npm was used.
Please mention your node.js, yarn and operating system version.
Windows 10, nodejs: v8.9.3, yarn: 1.3.2, npm: 5.5.1
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
I would say this is a bug..
What is the current behavior?
Angular compiler outputs the following after changing the package management to yarn (from npm):
ERROR in yarn-cache/v1/npm-@schematics/angular-0.1.11-b5f15320bbb60969d66c76a8ef6545058ac81ece/application/other-files/app.component.ts(4,31): error TS1136: Property assignment expected.
yarn-cache/v1/npm-@schematics/angular-0.1.11-b5f15320bbb60969d66c76a8ef6545058ac81ece/application/other-files/app.component.ts(4,32): error TS1109: Expression expected.
yarn-cache/v1/npm-@schematics/angular-0.1.11-b5f15320bbb60969d66c76a8ef6545058ac81ece/application/other-files/app.component.ts(4,33): error TS1146: Declaration expected.
yarn-cache/v1/npm-@schematics/angular-0.1.11-b5f15320bbb60969d66c76a8ef6545058ac81ece/application/other-files/app.component.ts(4,34): error TS1109: Expression expected.
yarn-cache/v1/npm-@schematics/angular-0.1.11-b5f15320bbb60969d66c76a8ef6545058ac81ece/application/other-files/app.component.ts(4,55): error TS1109: Expression expected.
.......
yarn-cache/v1/npm-@schematics/schematics-0.0.11-c8f70f270ed38f29b2873248126fd59abd635862/blank/schematic-files/src/name@dasherize/index.ts(6,17): error TS1003: Identifier expected.
yarn-cache/v1/npm-@schematics/schematics-0.0.11-c8f70f270ed38f29b2873248126fd59abd635862/blank/schematic-files/src/name@dasherize/index.ts(6,18): error TS1139: Type parameter declaration expected.
.......
yarn-cache/v1/npm-karma-1.7.1-85cc08e9e0a22d7ce9cca37c4a1be824f6a2b1ae/config.tpl.ts(13,18): error TS1109: Expression expected.
yarn-cache/v1/npm-karma-1.7.1-85cc08e9e0a22d7ce9cca37c4a1be824f6a2b1ae/config.tpl.ts(13,30): error TS1109: Expression expected.
.......
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
I would think that there would be no changes needed in our code, when the package manager is changed. As I understand, yarn still works on npm-"backend"? There is no more information printed and I don't know what to do, because I have no deeper knowledge of how yarn is working with it's cached dependencies, because I'm "only" a angular(5) developer who is using yarn for package management.
What would be the way to proceed? I've switched from npm to yarn, because sometimes uncontrollable errors appeared when npm re-installs were done.. but the dependencies were correct when npm was used.
Please mention your node.js, yarn and operating system version.
Windows 10, nodejs: v8.9.3, yarn: 1.3.2, npm: 5.5.1
The text was updated successfully, but these errors were encountered: