Skip to content
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

Wiki update for latest Firebase and AngularFire2 #2108

Open
ravivit9 opened this issue Oct 20, 2017 · 5 comments
Open

Wiki update for latest Firebase and AngularFire2 #2108

ravivit9 opened this issue Oct 20, 2017 · 5 comments

Comments

@ravivit9
Copy link

ravivit9 commented Oct 20, 2017

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[ x] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior
With latest firebase and angularfire2 not working.
screen shot 2017-10-24 at 16 32 09

Expected behavior
With latest firebase and angularfire2 seed must be working after including the 3rd party libraries as per wiki guidelines.

Minimal reproduction of the problem with instructions

Download NPM Modules

"angularfire2": "^5.0.0-rc.3",

"firebase": "^4.6.0"

In project.config.ts

// Add packages (e.g. ng2-translate)
let additionalPackages: ExtendPackages[] = [
  {
    name: 'firebase',
    path: 'node_modules/firebase/',
    packageMeta: {
      main: 'app.js',
      defaultExtension: 'js'
    }
  },
  {
    name: 'angularfire2',
    path: 'node_modules/angularfire2/',
    packageMeta: {
      main: 'angularfire2.js',
      defaultExtension: 'js'
    }
  }
];
//
this.addPackagesBundles(additionalPackages);

In app.module.ts

import { AngularFireModule } from 'angularfire2';
const FIREBASE_APP_CONFIG = {
apiKey: '',
authDomain: '',
databaseURL: '',
projectId: '',
storageBucket: '',
messagingSenderId: ''
};

@NgModule({
imports: [BrowserModule, HttpModule, AppRoutingModule, AboutModule, HomeModule, SharedModule.forRoot(),
AngularFireModule.initializeApp(FIREBASE_APP_CONFIG)
],

What is the motivation / use case for changing the behavior?
To use latest version of firebase and angularfire2

Please tell us about your environment:
Mac, npm,

  • Angular Seed Version: ab4a987
    ab4a987

  • Node: node --version = 5.4.2

@ravivit9
Copy link
Author

Hi, Just wanted to touch base with regards to this ticket, will there an road map to support angularfire2 / firestore within the seed. Appreciate all the hard work done by the seed contributors.

@mgechev
Copy link
Owner

mgechev commented Nov 12, 2017

Hey @ravivit9, the seed supports AngularFire2, it's only a matter of configuration. Since there are issues with higher priority (migration to Angular version 5 and support of ngc's watch mode), I'd recommend you to take a look at SystemJS' docs.

@ravivit9
Copy link
Author

@mgechev, I understand the you guys are busy in stepping up the seed to next level.

Yes I agree it's a matter of configuration but that is core to our angular-seed and we if load the firebase and angularfire2 libraries in proj.config.js as above described it doesn't work. This is how I use to load the previous versions and other external dependencies like material design2 version.

So for time being do I need to use systemjs to load the external dependencies until a fix or wiki update can be made?

Thanks.

@kelyane
Copy link

kelyane commented Jan 13, 2018

I am still getting the same problem. any solution?

@ravivit9
Copy link
Author

I just pulled recent update of the seed after few months but I am still having an issue in including firebase, meanwhile I am progressing in my original repo of my project. Hopefully the seed will allow us to configure firebase and material design from project.config.js.

I tried using SystemJS route but that didn't worked out too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants