Skip to content

tsconfig outDir parameter failing #11156

Closed

Description

@nitinet

Since i updated the typescript compiler, my tsc wasn't working. I experimented and as soon as i remove outDir parameter from compiler options in tsconfig.config file, it is now working.

TypeScript Version: 2.0.3

Activity

  1. mhegazy commented on Sep 26, 2016

    @mhegazy
    Contributor

    Can you share more information. Please share a self contained test along with the expected output, and the actual output.

  2. nitinet commented on Sep 30, 2016

    @nitinet
    Author

    The issue is with --outDir option in the tsconfig file. When i removed the option, now its working fine. I didn't got down deeper. Please let me know if more info is needed.

  3. mhegazy commented on Sep 30, 2016

    @mhegazy
    Contributor

    The issue is with --outDir option in the tsconfig file

    can you elaborate on how it is failing, what is the current output?

  4. nitinet commented on Oct 1, 2016

    @nitinet
    Author

    There is no output. Just that the javascript files are not getting generated from the ts files.

  5. tom-konda commented on Oct 7, 2016

    @tom-konda

    I have a similar problem on TypeScript 2.0.3.
    I specified outDir parameter end with "../" but tsc command didn't generate any .js files.
    When I run same command on TypeScript 1.8.10, .js files were generated successfully.

    I tested on this gist files.

  6. mhegazy commented on Oct 18, 2016

    @mhegazy
    Contributor

    Thanks Tom Konda (@tom-konda) for the repro. This looks like the same issue as #11621.

    If you do not have exclude property set, it is implicitly set to ["node_modules", .., <outdir>]. since your outDir is a parent directory of your source directory, no files are included in the compilation.

    to override this behavior specify empty exclude array.

  7. added
    DuplicateAn existing issue was already created
    and removed
    Needs More InfoThe issue still hasn't been fully clarified
    on Oct 18, 2016
  8. mhegazy commented on Oct 18, 2016

    @mhegazy
    Contributor

    I have also filed #11156 to track raising an error when no files are found to compile.

  9. locked and limited conversation to collaborators on Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    DuplicateAn existing issue was already created

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions