-
Notifications
You must be signed in to change notification settings - Fork 181
Adding elements from universal starter with this one #77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @beckmeindia — I'm sorry but I haven't had a chance to try angular universal yet. 😕 |
Hey @r-park Could you please help? Thanks, Here are the errors and warnings that I get on my terminalts-loader: Using [email protected] and C:\Users\gemini\Desktop\universal-starter
r 'directory' .//angularfire2.ts in C:\Users\gemini\Desktop\universal-starter\no
t resolve 'file' or 'directory' .//utils/firebase_list_observable.ts in C:\Users
esolve 'file' or 'directory' .//utils/firebase_list_factory.ts in C:\Users\gemin
ectory' .//tokens.ts in C:\Users\gemini\Desktop\universal-starter\node_modules\a
not resolve 'file' or 'directory' .//utils/firebase_object_observable.ts in C:\U
'directory' .//utils/utils.ts in C:\Users\gemini\Desktop\universal-starter\node
resolve 'file' or 'directory' .//utils/firebase_object_factory.ts in C:\Users\g
Cannot resolve 'file' or 'directory' .//providers/firebase_sdk_auth_backend.ts i
or 'directory' .//providers/auth.ts in C:\Users\gemini\Desktop\universal-starte
le' or 'directory' .//database/database.ts in C:\Users\gemini\Desktop\universal-
e 'file' or 'directory' .//providers/auth_backend.ts in C:\Users\gemini\Desktop
e 'file' or 'directory' .//utils/query_observable.ts in C:\Users\gemini\Desktop
[nodemon] 1.9.2 |
Hey @beckmeindia WARNING in ./~/angularfire2/angularfire2.js
Cannot find source file './/angularfire2.ts': Error: Cannot resolve 'file' or 'directory' .//angularfire2.ts in C:\Users\gemini\Desktop\universal-starter\node_modules\angularfire2 These warnings are being emitted by the webpack The messages are annoying but they shouldn't stop the app from running. You can always comment out the preLoaders section of your webpack config, or alternatively you can exclude angularfire2: const path = require('path');
preLoaders: [
// needed to lower the filesize of angular due to inline source-maps
{ test: /\.js$/, loader: 'source-map-loader', exclude: [
path.resolve('./node_modules/angularfire2')
]}
] I don't think the |
Hey @r-park If I share the repository with you, could you please have a look at the setup/config to make sure I am not making some gaping mistakes? |
Sure I can take a quick look. |
I have added the present repository here https://github.com/beckmeindia/universal-angularfire2 I have kept the angularfire2, firebase & firebase-tools files in the node-modules so that in case there is an error there, I could know. Will be waiting for your review. Thanks, |
@beckmeindia I checked out your repo and tried it out. The DI exceptions are raised during server-side rendering, partly because the AngularFire2 providers are missing form At a glance, it doesn't look like |
Okay. Thanks for reviewing it. Thanks a lot again!
|
Hey,
First of all I wanted to thank you for writing a great starter for angularfire2 with webpack.
It is perfect and I am using it to build my website.
The only problem I faced was the use of angular-universal. They too have a starter but I am using this because it doesn't have Firebase integrated.
Could you please tell me how to integrate the angular-universal with this. I have gone through all the docs but could not find a way out.
Cheers,
Rahul
The text was updated successfully, but these errors were encountered: