problem with external imports in aurelia

[lucamorelli]

Hi,
I'm using visual studio code to reproduce this sample in typescript

http://odetocode.com/blogs/scott/archive/2015/02/18/using-jspm-with-visual-studio-2015-and-asp-net-5.aspx

all works fine until I arrive at the point 4 and try to use moment. I follow the instructions, install the package using jspm, but I have the error message that cannot find this module, and the source files are not compiled.

Am I missing something?

[lucamorelli]

I tried to install tsd inside this project and is giving to me some problems, with a lot of errors: looks like ts I trying to recompile the content of the /node_modules/tsd/build and find a lot of missing references.

[lucamorelli]

I solved the first problem setting to false noEmitOnError in the tsconfig file, but I would like to find a better solution

[mhegazy]

I tried to install tsd inside this project and is giving to me some problems, with a lot of errors: looks like ts I trying to recompile the content of the /node_modules/tsd/build and find a lot of missing references.

The probelm is that tsconfig.json does not support execludes. this is tracked by #1927. So it is teling the compiler to include *__.ts in the current directory, which includes your tsd sources as well. To workaround this, in tsconfig,add a "files" entry and list your files, this will not include all files.

but I have the error message that cannot find this module, and the source files are not compiled.

As you mentioned later you also need a reference to moment.d.ts.

[lucamorelli]

thanks, add my application ts files in the files section solved several problems. I see that enabling es 6 output generates a few errors in the moment.d.ts file too.

[mhegazy]

if it is:

error TS1203: Export assignment cannot be used when targeting ECMAScript 6 or higher

This has been fixed in #2929, and should be in master now.

[lucamorelli]

I have some errors like these, using visual studio code that uses tsconfig.json :
App/contact-list.ts(1,31): error TS2307: Cannot find external module 'aurelia-event-aggregator'.
App/loading-indicator.ts(1,23): error TS2307: Cannot find external module 'nprogress'.
App/loading-indicator.ts(2,32): error TS2307: Cannot find external module 'aurelia-framework'.

I suppose this may be happen when I'm using new frameworks when thd .d.ts is not still available and/or complete.

btw: always talking about visual studio code, looks like that similar scenario when I compile I found 0 errors, as I start to write something detect a few errors

[DanielRosenwasser]

Yeah, that sounds like a .d.ts issue. Where'd you get your definitions from? DefinitelyTyped doesn't seem to have it yet.

[lucamorelli]

found this

https://github.com/cmichaelgraham/aurelia-typescript

[mhegazy]

@cmichaelgraham can you point @lucamorelli to the latest .d.ts for aurelia?

[cmichaelgraham]

we are now automatically generating the aurelia .d.ts files, one per repo, using a typescript port of the aurelia libraries. you can find a working sample of the results here with the .d.ts files here

We are still working out some kinks. let me know if you have troubles.

[lucamorelli]

thanks for the link. I'm still working on it to see if is possibile to use jspm as in the normal javascript version. nothing against the solution you have found, but in this solution when you have a problem with the program you don't know if it is part of the problem.

[cmichaelgraham]

you should be able to use the .d.ts files above with your jspm solution. i'm happy to help if you run into trouble

[lucamorelli]

I copied directly all the sample in an asp.net 5 proejct: runs with chrome but not with ie.
Tried to changed the index page configuring the load via jspm (I think I already installed the jspm packages during previous tests) but doesn't show the startup screen neither.
seems that this alternate configuration is due to the esri library, that requires es5 compilation and amd module support.
This may be a problem in production if someone start to develop using es 6 and must add some "legacy" library during development.
Is there some way to wrap this library in a es 6 module and let the two things coexists?