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

Traceur error when using NgModule inside Rc.5 #10881

Closed
roby2001 opened this issue Aug 17, 2016 · 5 comments
Closed

Traceur error when using NgModule inside Rc.5 #10881

roby2001 opened this issue Aug 17, 2016 · 5 comments

Comments

@roby2001
Copy link

roby2001 commented Aug 17, 2016

Simply updating my application from Rc.4 to Rc.5 without changing code works. Yet when I try to change my bootstrap to use an NgModule and such I recieve the following error:

image

I stripped down the project to the most basic version I could think of ( like in the 5 mins quickstart ), the error persists.

My first guess was that system.js was not properly mapping traceur, yet when I went over the 5 mins quickstart / my node modules the only code references I could find to traceur were in system.src.js from @angular.

What is causing this error and what should I do in order to fix it? Why is it requesting : localhost:3000\traceur only when I'm using NgModule ?

@pietie
Copy link

pietie commented Aug 17, 2016

Do you have any multi line comments?

I had traceur related errors after upgrading to rc5. Apparently angular bugs out on the parsing of /* */ comments so after I removed those my traceur errors went away.

@roby2001
Copy link
Author

@pietie this totally goes on my list of top 10 retarded bugs ... Thanks a bunch!

@Robert3191
Copy link

Offtopic: I can confirm. He was very frustrated that day. :))

@sweeneyrobb
Copy link

spent a fair number of cycles trying to resolve this very issue. thanks for posting this. saved me more hours hunting for what was wrong.

@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 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants