Valid TypeScript generates build error

[bdphil86]

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Windows 10

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.24
node: 7.2.0
os: win32 x64

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

Yes. App was created using CLI.

I like to export all items at the end of my file rather than inline. So, I am seeing an error when I have valid code written as:

...
class SomeComponent {
  ...
}

export { SomeComponent }

However, if I change the placement of the export, the error goes away:

...
export class SomeComponent {
  ...
}

This shouldn't generate an error considering it is valid TS.

The log given by the failure.

Normally this include a stack trace and some more information.

The error is similar to:
ERROR in Error encountered resolving symbol values statically. Reference to a non-exported class SomeComponent. Consider exporting the class (position 6:1 in the original .ts file), resolving symbol SomeComponent in C:/path/src/app/some/some.component.ts

Mention any other details that might be useful.

---

Thanks! We'll be in touch soon.

[hansl]

Could you try to change your tsconfig.json to add "files": ["main"] at the end, then run node_modules/.bin/ngc? If it results in the same error (which I think it will), please file an issue against angular itself with that information; it's a problem with the code generator inside Angular offline compiler, and not the CLI itself.

Cheers.

[angular-automatic-lock-bot]

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.}