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

Removed option "contextAsConfigBasePath" because the context given to… #688

Merged
merged 6 commits into from
Jan 20, 2018

Commits on Dec 4, 2017

  1. Removed option "contextAsConfigBasePath" because the context given to…

    … the loader is NOT the webpack.context but the directory of the current file. This makes the option useless.
    
    As there is no possibility to get access to the webpack.context in a webpack loader, a new option which serves the same purpose is introduced.
    
    Added option "context" (string). Allows to directly set the base path when parsing the tsconfig file. Has to be an absolute path.
    christiantinauer committed Dec 4, 2017
    Configuration menu
    Copy the full SHA
    34be34d View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    921ed28 View commit details
    Browse the repository at this point in the history

Commits on Dec 5, 2017

  1. Fixed tsconfig.json in test "option-context" to work with older TS ve…

    …rsions.
    Christian Tinauer committed Dec 5, 2017
    Configuration menu
    Copy the full SHA
    bc2254d View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    17dc8e5 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    c598da3 View commit details
    Browse the repository at this point in the history

Commits on Jan 20, 2018

  1. Configuration menu
    Copy the full SHA
    c6354c1 View commit details
    Browse the repository at this point in the history