I am using universal-starter as backbone.
When my client starts, it read a token about user info from localStorage.
@Injectable()
export class UserService {
foo() {}
bar() {}
loadCurrentUser() {
const token = localStorage.getItem('token');
// do other things
};
}
Everything works well, however I got this in the server side (terminal) because of server rendering:
EXCEPTION: ReferenceError: localStorage is not defined
I got the idea from ng-conf-2016-universal-patterns that using Dependency Injection to solve this. But that demo is really old.
Say I have these two files now:
main.broswer.ts
export function ngApp() {
return bootstrap(App, [
// ...
UserService
]);
}
main.node.ts
export function ngApp(req, res) {
const config: ExpressEngineConfig = {
// ...
providers: [
// ...
UserService
]
};
res.render('index', config);
}
Right now they use both same UserService. Can someone give some codes to explain how to use different Dependency Injection to solve this?
If there is another better way rather than Dependency Injection, that will be cool too.
UPDATE 1 I am using Angular 2 RC4, I tried @Martin's way. But even I import it, it still gives me error in the terminal below:
Terminal (npm start)
/my-project/node_modules/@angular/core/src/di/reflective_provider.js:240 throw new reflective_exceptions_1.NoAnnotationError(typeOrFunc, params); ^ Error: Cannot resolve all parameters for 'UserService'(Http, ?). Make sure that all the parameters are decorated with Inject or have valid type annotations and that 'UserService' is decorated with Injectable.
Terminal (npm run watch)
error TS2304: Cannot find name 'LocalStorage'.
I guess it is somehow duplicated with the LocalStorage
from angular2-universal
(although I am not using import { LocalStorage } from 'angular2-universal';
), but even I tried to change mine to LocalStorage2
, still not work.
And in the meanwhile, my IDE WebStorm also shows red:
BTW, I found a import { LocalStorage } from 'angular2-universal';
, but not sure how to use that.
UPDATE 2, I changed to (not sure whether there is a better way):
import { Injectable, Inject } from '@angular/core';
import { Http } from '@angular/http';
import { LocalStorage } from '../../local-storage';
@Injectable()
export class UserService {
constructor (
private _http: Http,
@Inject(LocalStorage) private localStorage) {} // <- this line is new
loadCurrentUser() {
const token = this.localStorage.getItem('token'); // here I change from `localStorage` to `this.localStorage`
// …
};
}
This solves the issue in UPADAT 1, but now I got error in the terminal:
EXCEPTION: TypeError: this.localStorage.getItem is not a function
In Angular 4 (and 5) you can easily deal with such issue with a simple function in the following way:
app.module.ts
If you have a server/client split file AppModule, place it in the
app.module.shared.ts
file - the function won't break your code - unless you need to enforce completely different behaviours for the server and client builds; if that’s the case, it could be wiser to implement a custom class factory instead, just like it has been shown in other answers.Anyway, once you're done with the provider implementation, you can inject the
LOCALSTORAGE
generic in any Angular component and check for the platform type with the Angular-nativeisPlatformBrowser
function before using it:It’s worth noting that, since the
getLocalStorage()
function will returnnull
if the window object isn’t available, you could just check forthis.localStorage
nullability and entirely skip the platform type check. However, I strongly recommend the above approach as that function implementation (and return value) might be subject to change in the future; conversely, theisPlatformBrowser
/isPlatformServer
return values are something that can be trusted by design.For more info, check out this blog post that I wrote on the topic.
I have no sufficient knowledge of preparing angular apps to run serverside. But in the similar scenario for react & nodejs, what needs to be done is to let server know what
localStorage
is. For example:Hope this can be of any help to you.
As stupid as this approach might seem, it is working, and I had to do none of the plumbing the other answers are suggesting.
Step 1
Install
localstorage-polyfill
: https://github.com/capaj/localstorage-polyfillStep 2
Assuming you followed this step: https://github.com/angular/angular-cli/wiki/stories-universal-rendering, you should have a file called,
server.js
in your project root folder.In this
server.js
add this:Step 3
Rebuild your project,
npm run build:ssr
, and all should work fine now.Does the above approach work? Yes, as far as I can tell.
Is it the best? Maybe not
Any performance issues? Not that I know of. Enlighten me.
However, as it stands now, this is the dumbest, most cleanest approach to getting my
localStorage
to passI don't think this is a good solution, but I was stucked with the same problem using aspnetcore-spa generator and solved it this way:
This condition prevents client code from running on the server-side where 'window' object doesn't exist.
I am having a similar issue with Angular 4 + Universal following steps here to configure a SPA that can render at client side or server side.
I am using oidc-client because I need my SPA to act as an OpenId Connect/Oauth2 client for my Identity Server.
The thing is that I was having the typical problem where localStorage or sessionStorage are not defined in server side (they only exist when there's a window object, therefore it wouldn't make sense for nodeJs to have these objects).
I have unsuccessfully tried the approach to mock the localStorage or sessionStorage and use the real one when in browser and an empty one in server.
But I came to the conclusion that for my needs I don't really need localStorage or sessionStorage to do anything in server side. If executed in NodeJs, simply skip the part where sessionStorage or localStorage is used, and the execution will then happen at client-side.
This would suffice:
In client-side rendering it prints:
Window is: object
In nodeJs it prints:
Window is: undefined
The beauty of this is that Angular Universal will simply ignore the execution/rendering at server side when there is no window object, BUT that execution will be working fine when Angular Universal sends the page with javascript to the browser, therefore even if I am running my app in NodeJs eventually my browser prints the following:
Window is: object
I know this is not a proper answer for those who really need to access localStorage or sessionStorage in server side, but for most of the cases we use Angular Universal simply to render whatever is possible to render in server side, and for sending the things that can't be rendered to the browser to work normally.
This is how we have it in our project, as per from this github comment: