X Tutup
Skip to content

remove traceur from the build pipeline#3974

Closed
rkirov wants to merge 2 commits intoangular:masterfrom
rkirov:ts_es5
Closed

remove traceur from the build pipeline#3974
rkirov wants to merge 2 commits intoangular:masterfrom
rkirov:ts_es5

Conversation

@rkirov
Copy link
Copy Markdown
Contributor

@rkirov rkirov commented Sep 3, 2015

npm traceur package is still used for traceur-runtime dependency.

@googlebot
Copy link
Copy Markdown

We found a Contributor License Agreement for you (the sender of this pull request) and all commit authors, but as best as we can tell these commits were authored by someone else. If that's the case, please add them to this pull request and have them confirm that they're okay with these commits being contributed to Google. If we're mistaken and you did author these commits, just reply here to confirm.

@rkirov
Copy link
Copy Markdown
Contributor Author

rkirov commented Sep 3, 2015

@pkozlowski-opensource The typescript version we are using produces bad -m system output. When trying to upgrade to a newer one I run into slew of other errors. I am sure that we can get it to work (maybe with some help from TS and system.js guys). However, since removing traceur has been pending for quite long on our task list, I rather go ahead with this option, because it just works.

Note that system.js is still used as a module loader for the commonjs output for the e2e and unit tests runs, which means that shouldn't affect consumers.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

update comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

+1

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done.

@alexeagle
Copy link
Copy Markdown
Contributor

Fix the failing tests.
Seems like a great next step to me. Do we have any bugs open for the problems with TS System emit?

@rkirov
Copy link
Copy Markdown
Contributor Author

rkirov commented Sep 3, 2015

@alexeagle the issue is the one you know about systemjs/systemjs#712 and from some local testing with typescript@next it looks like it is fixed at TS head. However, upgrading TS leads to other jankiness. Lets get this in, upgrade TS and then try to flip es5 output back to 'system' (if we are still convinced that is important).

@rkirov rkirov force-pushed the ts_es5 branch 3 times, most recently from 2bd178a to f8fff51 Compare September 4, 2015 01:13
@rkirov
Copy link
Copy Markdown
Contributor Author

rkirov commented Sep 4, 2015

PTAL

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

doesn't this test now test that we don't have source mapping at all?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Nope, before we did ts -> es6 -> es5 in two shots, and didn't properly merge the sourcemaps for the two jumps. So in the test we had to decode twice (once per transpilation).

Now, we have a direct ts -> es5, so we just need to read in one source map and compare with the original. Notice we read the expected line from modules/examples/src/sourcemap/index.ts

@IgorMinar IgorMinar assigned IgorMinar and unassigned alexeagle Sep 4, 2015
@IgorMinar IgorMinar added the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label Sep 4, 2015
@alexeagle
Copy link
Copy Markdown
Contributor

Note that we already cherry-picked one upstream TS-system fix into the TS we use for Angular
alexeagle/TypeScript@6470f8e
so we can easily do that again if we are missing another bugfix.

@rkirov
Copy link
Copy Markdown
Contributor Author

rkirov commented Sep 4, 2015

@alexeagle right, but I rather put effort into bringing newer versions that are released on npm (currently looks like 1.6.0-beta), and avoid too much cherry-picking. Also system vs commonjs module format output doesn't seem critical to me, since system.js loads them both fine.

@rkirov rkirov added action: merge The PR is ready for merge by the caretaker and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Sep 4, 2015
@mary-poppins
Copy link
Copy Markdown

Merging PR #3974 on behalf of @rkirov to branch presubmit-rkirov-pr-3974.

@mary-poppins mary-poppins removed the action: merge The PR is ready for merge by the caretaker label Sep 4, 2015
This removes traceur from the compilation step in broccoli. Broccoli now
transpiles to es5 using the typescript compiler.
System output does not work at the current versions of TS and
system.js. Will revisit after upgrading TS.

Removes unused traceur tooling.
@rkirov rkirov added the action: merge The PR is ready for merge by the caretaker label Sep 4, 2015
@mary-poppins
Copy link
Copy Markdown

Merging PR #3974 on behalf of @rkirov to branch presubmit-rkirov-pr-3974.

@mary-poppins mary-poppins removed the action: merge The PR is ready for merge by the caretaker label Sep 4, 2015
@rkirov rkirov closed this in e9ad100 Sep 4, 2015
@angular-automatic-lock-bot
Copy link
Copy Markdown

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 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

X Tutup