mgechev / mgechev/angular-seed

speeding up build on windows - Failed to parse file

Open
#2,154 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
4.5k
Forks
1.4k
PR merge metrics
No merged PRs in 30d

Description

Thanks in advance for any help.

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior
Running the below command as per instructions in speeding up build on windows wiki page
tsc --project tsconfig.json

throws error:
error TS5014: Failed to parse file 'tsconfig.json/tsconfig.json': Unexpected token u in JSON at position 0.

Expected behavior
compile tools to js files

Minimal reproduction of the problem with instructions
tsc --project tsconfig.json

Please tell us about your environment:
OS: Windows 10
IDE: VSCode v1.17.2
NPM v4.0.2
node v 6.9.1

  • Angular Seed Version: 234a5fed2bc74ec6dceb32b6ddf09dcc504b4083

  • Node: node --version = 6.9.1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing tsc --project tsconfig.json on Windows 10 with the reported Node 6.9.1 and TypeScript setup, then inspect how tsconfig.json is being resolved. Compare the result with the speeding-up-build-on-Windows instructions; done means the tools compile to JavaScript without the TS5014 parsing error.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.