Skip to content

'ng lint' fails with angular 2.0.2 #2567

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

Closed
vkniazeu opened this issue Oct 7, 2016 · 2 comments
Closed

'ng lint' fails with angular 2.0.2 #2567

vkniazeu opened this issue Oct 7, 2016 · 2 comments

Comments

@vkniazeu
Copy link

vkniazeu commented Oct 7, 2016

OS?

Windows 10 Pro

Versions.

angular-cli: 1.0.0-beta.15
node: 6.7.0
os: win32 x64
npm: 3.10.8

Repro steps.

Updated from angular 2.0.1 to 2.0.2, ts-node from 1.3.0 to 1.4.0
ng lint fails with the following without listing any errors.

tslint "src/**/*.ts"
Lint errors found in the listed files.

The log given by the failure.

npm-debug.log stack trace:

13 info lifecycle [email protected]~lint: Failed to exec lint script
14 verbose stack Error: [email protected] lint: `tslint "src/**/*.ts"`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Users\...\npm\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Users\V...\npm\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:877:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)

Mention any other details that might be useful.

Reverting to ts-node 1.3.0 did not help. Still errors out.

@filipesilva
Copy link
Contributor

@vkniazeu see #867 (comment)

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants