Skip to content

Conversation

@devversion
Copy link
Member

@devversion devversion commented Jan 22, 2017

  • Fixes the invalid sourcemaps for the dev-app and e2e-app.

    The sourcemaps are currently invalid because the sourcesContent couldn't be read due to invalid paths.

This issue is now noticeable because gulp-typescript made some changes in regards to the sourcemaps. (See here)

* Fixes the invalid sourcemaps for the dev-app and e2e-app.

> The sourcemaps didn't include the content of the source file because the paths were mapped incorrectly (due to a combination of `outDir` and `mapRoot`)
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 22, 2017
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Jan 23, 2017
@andrewseguin andrewseguin merged commit 6b36156 into angular:master Jan 24, 2017
@devversion devversion deleted the build/fix-sourcemaps branch January 25, 2017 16:09
devversion added a commit to devversion/material2 that referenced this pull request Jan 25, 2017
* No longer use the `gulp-typescript` gulp package that tries to take care of several options like `sourceMaps` or `declarations`.
* Don't generate declarations when serving the `demo-app`. (Slows down testing)

Advantages:

* Use the `Typescript` compiler CLI to ensure that the `NGC` also works with our `tsconfig.json` files.
* No longer makes our TypeScript build dependent to an external plugin (~with magic)
* Fixes issues like invalid sourceMaps from `gulp-typescript`: angular#2753
* Allows us to take use of all TypeScript features (e.g forbidden features in `gulp-typescript)
* This should help for our planned `tsconfig.json` file reduction.
@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

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants