Failing to compile about the-traveler

[alexanderwe]

Hi @cozyrobinson, thank you for opening this issue 👍

I am not very proficient with Angular on particular but it seems that this is not directly related to the traveler package itself. At least this is what I would assume by the error log you provided.

Do you have any code or repository which is a minimal reproducible example, where you can show the error ? So basically which I can clone and test locally on my machine ?

[cozyrobinson]

Thanks for responding!

I use bitbucket, if that's okay: https://bitbucket.org/drift_cody/testiny/overview

[alexanderwe]

Sure, Bitbucket is not a problem. But it seems your repository does not contain any code ?

[cozyrobinson]

Oops, try now.

[alexanderwe]

Thanks a lot for the code

I checked your project and you are right, with the-traveler as a dependency it doesn't compile. At first I was a little bit confused but then I quickly realised what's the problem here. I am sorry that I did not thought of it on the first place.

The dependencies of the the-travler are depend on a Node environment. For example the fs module which will give you access to the file system. It is used to interact with the manifest files. But the angular-cli will create a browser application which does not run in a Node environment. That is why you get all those errors of modules not being found while compiling. They are simply not available in the browser. For reference see this comment: angular/angular-cli#8272 (comment)

So you are only able to use the library in a Node environment.

[cozyrobinson]

Ah, bummer. So there's no way at all to run this with my project?

…

On Sun, Nov 18, 2018, 2:01 PM Alexander Weiß ***@***.*** wrote: Thanks a lot for the code I checked your project and you are right, with the-traveler as a dependency it doesn't compile. At first I was a little bit confused but then I quickly realised what's the problem here. I am sorry that I did not thought of it on the first place. The dependencies of the the-travler are depend on a Node environment. For example the fs module which will give you access to the file system. It is used to interact with the manifest files. But the angular-cli will create a browser application which does not run in a Node environment. That is why you get all those errors of modules not being found while compiling. They are simply not available in the browser. For reference see this comment: angular/angular-cli#8272 (comment) <angular/angular-cli#8272 (comment)> So you are only able to use the library in a Node environment. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Aq-AfVr_APAe8ZOrZ56aSHK2R7kqJMziks5uwbyygaJpZM4YfASC> .

[alexanderwe]

I am really sorry to say this, but if you want to use it as a browser module - no. Unfortunately there is now way to use it since it relies on other modules which are only available in a Node environment.

What you could do, is set up a Node server, which is running the library and expose it results trough an API but I think this is not what you want to do. Just a thought that came into my mind.

[alexanderwe]

I will close this issue for now. If you still have some other doubts or questions please do not hesitate to ask