Using module with SSR from angular cli gives import error about ngx-scroll-to

[nicky-lenaers]

@jacobedawson @jimmy-tfp I'm working on this issue. Will be resolved soon!

[nicky-lenaers]

Hi @jimmy-tfp, thank you for submitting your issue. I will be investigating this soon!

[jacobedawson]

@nicky-lenaers I just ran into this issue as well - the error only came up while building for SSR, same error as what @jimmy-tfp reported.

Thanks for your work on the module but I would say until this issue is resolved you might want to remove the mention on the repo homepage that this module works with SSR.

[jacobedawson]

@nicky-lenaers thanks for your effort dude, in all other aspects it's a great module :)

[nicky-lenaers]

@jacobedawson @jimmy-tfp I did a full repo overhaul to enforce a package called ng-packagr. This module should package everything up properly. I just release 0.4.0-alpha.3, which includes support for SSR builds. I tested it on my own repo and it works.

I'd like to get your feedback on whether it works or not.

Thanks, your feedback is much appreciated!

[jacobedawson]

Hi @nicky-lenaers - I just installed 0.4.0-alpha.3 and I got this error during compilation (no other changes made - just installed ngx-scroll-to, added imports in module.ts, set up the service from this repo):

 ERROR in Error: Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 194:50 in the original .ts file), resolving symbol NgModule in ... etc

[nicky-lenaers]

@jacobedawson Thank you for reporting this. I came across quiet a hot issue topic that references this issue. It seems there could be multiple factors that cause this error. Even outside of the scope of this module. The fact that I have a working example in a repo confirms that.

I'd really like to help you with this. Do you mind setting up a small example repo or plunkr with your setup (or share the repo you already have if possible), so I'm able to properly figure out what causes this error?

Thanks in advance.

[jacobedawson]

@nicky-lenaers yo dude - sure thing, will have a look tomo morning (bedtime in berlin...zzz) and get back to you, cheers!

[nicky-lenaers]

Sure man, same thing in your neighbor Netherlands :-) let me know when you got something!

[nicky-lenaers]

@jacobedawson I've been doing research into this issue. It seems to not be related to this module specifically. My suggestion is to check your installed versions of Angular itself and go through topics that address your issue.

Thanks again for your feedback, this is much appreciated!

Closing this issue due to irrelevance to the module.