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

adding: tsBuildInfoFile included in TypeScript 3.4 #663

Merged
merged 1 commit into from
Apr 5, 2019
Merged

adding: tsBuildInfoFile included in TypeScript 3.4 #663

merged 1 commit into from
Apr 5, 2019

Conversation

Luxcium
Copy link
Contributor

@Luxcium Luxcium commented Apr 5, 2019

{

  "issue": {
    "asPer": [
      "https://devblogs.microsoft.com/typescript/announcing-typescript-3-4/",
      "https://www.typescriptlang.org/docs/handbook/compiler-options.html"
    ],
    "option": "--tsBuildInfoFile",
    "type": "string",
    "default": ".tsbuildinfo",
    "description": "Specify what file to store incremental build information in."
  },
  "problems": [
    {
      "description": "for the moment receiving this error message:",
      "when": "using : tsc -d --tsBuildInfoFile './build/lib/.tsbuildinfo'",
      "message": "error TS6064: Option 'tsBuildInfoFile' can only be specified in 'tsconfig.json' file."
    },
    {
      "description": "and then this error message if in tsconfig.json:",
      "when": "unsing :    '\"tsBuildInfoFile\": \"./build/lib/.tsbuildinfo\",' ",
      "message": "'Option de compilateur 'tsBuildInfoFile' inconnue.' (unknown option)"
    }
  ],
  "more": [
    " By default with these settings, when we run tsc, TypeScript will look for a file called .tsbuildinfo in the output directory (./lib). If ./lib/.tsbuildinfo doesn’t exist, it’ll be generated. But if it does, tsc will try to use that file to incrementally type-check and update our output files.",
    " These .tsbuildinfo files can be safely deleted and don’t have any impact on our code at runtime – they’re purely used to make compilations faster. We can also name them anything that we want, and place them anywhere we want using the --tsBuildInfoFile flag.",
    {
      "where": "front-end.tsconfig.json",
      "compilerOptions": {
        "incremental": true,
        "tsBuildInfoFile": "./buildcache/front-end",
        "outDir": "./lib"
      },
      "include": ["./src"]
    }
  ]
}

{
  "issue": {
    "asPer": [
      "https://devblogs.microsoft.com/typescript/announcing-typescript-3-4/",
      "https://www.typescriptlang.org/docs/handbook/compiler-options.html"
    ],
    "option": "--tsBuildInfoFile",
    "type": "string",
    "default": ".tsbuildinfo",
    "description": "Specify what file to store incremental build information in."
  },
  "problems": [
    {
      "description": "for the moment receiving this error message:",
      "when": "using : tsc -d --tsBuildInfoFile './build/lib/.tsbuildinfo'",
      "message": "error TS6064: Option 'tsBuildInfoFile' can only be specified in 'tsconfig.json' file."
    },
    {
      "description": "and then this error message if in tsconfig.json:",
      "when": "unsing :    '\"tsBuildInfoFile\": \"./build/lib/.tsbuildinfo\",' ",
      "message": "'Option de compilateur 'tsBuildInfoFile' inconnue.' (unknown option)"
    }
  ],
  "more": [
    " By default with these settings, when we run tsc, TypeScript will look for a file called .tsbuildinfo in the output directory (./lib). If ./lib/.tsbuildinfo doesn’t exist, it’ll be generated. But if it does, tsc will try to use that file to incrementally type-check and update our output files.",
    " These .tsbuildinfo files can be safely deleted and don’t have any impact on our code at runtime – they’re purely used to make compilations faster. We can also name them anything that we want, and place them anywhere we want using the --tsBuildInfoFile flag.",
    {
      "where": "front-end.tsconfig.json",
      "compilerOptions": {
        "incremental": true,
        "tsBuildInfoFile": "./buildcache/front-end",
        "outDir": "./lib"
      },
      "include": ["./src"]
    }
  ]
}
@Luxcium
Copy link
Contributor Author

Luxcium commented Apr 5, 2019

the only place I found something related to this problem googling online was the issue opened by @leemhenson in Microsoft/TypeScript/issues #30412

@madskristensen madskristensen merged commit d45c55a into SchemaStore:master Apr 5, 2019
@madskristensen
Copy link
Contributor

Thanks

@Luxcium Luxcium deleted the patch-1 branch April 10, 2019 04:49
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.

2 participants