var appControllers = angular.module('appControllers', ['firebase']);

This variable is not referenced anywhere. I deleted it and its reference in "myApp". The project still works.

As stated the delete gifts is faulty and should delete only the one click on and not all of them.

Linux pad-lawrencekimsey-com 5.0.9-301.fc30.x86_64 #1 SMP Tue Apr 23 23:57:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

[lk@pad-lawrencekimsey-com angulardata]$ node -v
v10.16.0
[lk@pad-lawrencekimsey-com angulardata]$ npm -v
6.9.0
[lk@pad-lawrencekimsey-com angulardata]$ git --version
git version 2.21.0
[lk@pad-lawrencekimsey-com angulardata]$

[lk@pad-lawrencekimsey-com angulardata]$ gulp
bash: gulp: command not found...

error displayed when adding a new user: firebaseUsers.$set is not a function

the code below is from authentication.js, lines 41 - 59 (see third from the end)

register: function(user) {
  return auth.$createUser({
    email: user.email,
    password: user.password
  }).then(function(regUser) {
    var ref = new Firebase(FIREBASE_URL+'users');
    var firebaseUsers = $firebaseObject(ref);     

from registrations
var userInfo = {
date : Firebase.ServerValue.TIMESTAMP,
regUser : regUser.uid,
firstname: user.firstname,
lastname : user.lastname,
email: user.email
}; //user info

    firebaseUsers.$set(regUser.uid, userInfo);
  }); //promise
}, //register

TypeError: firebaseUsers.$set is not a function
at authentication.js:57
at angular.js:14551
at m.$get.m.$eval (angular.js:15830)
at m.$get.m.$digest (angular.js:15641)
at angular.js:15869
at e (angular.js:5387)
at angular.js:5659

I looked into the docs and there isn't a $set method in angularfire

The command $gulp throws this error:
$ gulp assert.js:350
throw err;
^ AssertionError [ERR_ASSERTION]: Task function must be specified

Hi Rey,

npm-install should be npm install just in case someone like me gets command not found error.

Hi Ray,

Love the courses at Lynda, but this video on" Installing the template" references a branch called Start that doesn't seem to exist.

I grabbed the Master, just thought you should know.

Keep up the great work.
Tim

Issue Overview

When running 'npm install' 15 vulnerabilities (1 low, 12 high, 2 critical) show up.

Is this simply a case of updating some of the

To be entirely honest I don't know if this is an issue or I am missing something.

Describe your environment

npm --version
7.0.10

node --version
v12.18.3

Steps to reproduce

Change directory to desktop:

Git clone https://github.com/planetoftheweb/angulardata.git

Change directory to 'angulardata'.

Run npm install

Expected behaviour

NPM installs modules without critical vulnerabilities

Current behaviour

npm WARN using --force Recommended protections disabled.
npm WARN audit Updating gulp-webserver to 0.5.0,which is a SemVer major change.
npm WARN audit Updating gulp to 4.0.2,which is a SemVer major change.
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.

A summary of the critical issues.

Run npm audit for details.
angulardata % npm audit

npm audit report

Severity: critical
Command Injection - https://npmjs.com/advisories/663
fix available via npm audit fix --force
Will install [email protected], which is a breaking change

debug <=2.6.8 || 3.0.0 - 3.0.1
Regular Expression Denial of Service - https://npmjs.com/advisories/534
fix available via npm audit fix --force
Will install [email protected], which is a breaking change
node_modules/tiny-lr/node_modules/debug

On this project and the prequel to it, I ran into an issue where I get an error message that says, "ReferenceError: primordials is not defined". After doing some googling, I found that this was happening because the project is on Gulp version 3 and I am running Node version 12. I did find this issue on StackOverflow https://stackoverflow.com/questions/55921442/how-to-fix-referenceerror-primordials-is-not-defined-in-node-js and the solution titled, "Fix it in one minute:" did fix my issue.

Hey Ray,

I'm taking your second angular course, and am following along well so far,
but when I got to ch02_02, I noticed the nav bar's CSS was clearly off.
so I looked at the CSS file found the "branding" class, and saw that the padding was this:
padding: 10px, 15px, 10px, 60px;
I changed the 60px to 15px and that seemed to fix it.

Curious, I looked at the CSS file for the ch02_02 branch.
It was a lot different in concerns to the "start" branch's CSS file.
This file didn't even have a padding element.
Copying the code, I replaced it with the existing code I had when I cloned the start branch.
Looking further, I saw that all of the branches's CSS files were good EXCEPT the start branch's.

Looks like it's a very simple fix. Keep up the great work on lynda.com. Look forward to more angular courses.