I am on macOS and these are my npm and node versions:

npm --v
6.9.0
node -v
v12.3.1

This is the log I get if running npm run setup as mentioned in documentation.

I also tried using node v10.16.0I and npm 6.9.0. Also tried using Yarn but I still run into warnings/errors. Which should be the latest version?

Can you point me to the right direction? Since the documentation requirement says node9.3.0 + and [email protected] + I thought that using newest stable versions would be fine, correct me if I am wrong.

Is your feature request related to a problem? Please describe. Currently Google authentication is provided as an app embedded feature, which is great! However this is not always the go-to authentication method for most apps.

Describe the solution you'd like It would be great to additionally have the option to register + login using the email and password firebase method. As an extra, additional parameters could be passed (for example "displayName", "logoURL" or accountType).

Describe the bug When creating a fresh bento starter, on a windows machine. When you check out and run the npm run setup in Vscode it causes the job to fail due to UNIX commands. To Reproduce Steps to reproduce the behavior:

1. Check out clean copy
2. Run npm run setup from vscode or command line
3. Select Y when asked about new repo
4. Error; Error: Command failed rm -Rf .git

Expected behavior A user shouldn't be expected to use git bash or similar UNIX wrapper on a windows machine to get started. You should stop using rimraf and do an OS check. If UNIX use 'rm -rf' as its more efficient than rimraf and then use the rd /s /q "path" for windows.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10 Enterprise / VSCODE June release
• Browser N/A
• Version N/A

Additional context This works fine from git bash, or similar wrapper. Fails on vscode using windows command prompt.

See below for error:

The following is to resolve issue #179

A quick explanation of the changes:

Added a new vue view called Register which handles the creation of a new user.

JS handles the auth and then after an update of the Photo and Display name is added, if its null it will do nothing but it shows us how to add a new photo / display name.

On the login page, two inputs were added for email and password and a new button that handles auth via email and password.

This should be a good start, let me know what you think and what we could do / need to do.

Describe the bug The recent release of 2.19.0 and 2.19.1 of eslint-plugin-import introduce some errors. Specifically installing 2.18.2 (and not running install as ^2.18.2) resolves this for now at least.

To Reproduce When adding the following peer dependency: [email protected] requires a peer of eslint-plugin-import@^2.18.2

npm i eslint-plugin-import@^2.18.2 will install 2.19.1 and result in the following errors (27 times for some version of):

error: Missing file extension for "@/router"

import router from ‘@/router’

Downgrading to 2.19.0 results in the following error:

ERROR  TypeError: Cannot read property 'value' of null
Occurred while linting /Users/md/www/bento-debug/src/misc/helpers.js:7

And 2.18.2 (the version before 2.19.0) seems to be the latest that runs without error, so be sure to install the dependency specific to that version unless this is resolved using:

npm i [email protected]

Additional context This is more a heads up for anyone recklessly installing peer dependencies (as I was) and then inheriting this mess of new errors. From what I have read, however, there may be some configuration options to help thwart this; perhaps along the lines of eslint-import-resolver-webpack eslint-import-resolver-webpack on npm site But I really don't know. Putting that link above as a resource for those that would know, not as a suggested solution.

I got this ..

zuhair@DESKTOP-K9ATPC4 MINGW64 ~/Desktop/Bento/bento-starter (master) $ npm i npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it!

[email protected] install C:\Users\zuhair\Desktop\Bento\bento-starter\node_modules\iltorb detect-libc prebuild-install || node-gyp rebuild

prebuild-install WARN install No prebuilt binaries found (target=10.15.3 runtime=node arch=x64 platform=win32)

C:\Users\zuhair\Desktop\Bento\bento-starter\node_modules\iltorb>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild ) gyp ERR! configure error gyp ERR! stack Error: Command failed: C:\Program Files\Python37\python.EXE -c import sys; print "%s.%s.%s" % sys.version_info[:3]; gyp ERR! stack File "", line 1 gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3]; gyp ERR! stack ^ gyp ERR! stack SyntaxError: invalid syntax gyp ERR! stack gyp ERR! stack at ChildProcess.exithandler (child_process.js:294:12) gyp ERR! stack at ChildProcess.emit (events.js:189:13) gyp ERR! stack at maybeClose (internal/child_process.js:970:16) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) gyp ERR! System Windows_NT 10.0.17763 gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" gyp ERR! cwd C:\Users\zuhair\Desktop\Bento\bento-starter\node_modules\iltorb gyp ERR! node -v v10.15.3 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm WARN [email protected] requires a peer of eslint-plugin-jsx-a11y@^6.1.1 but none is installed. You must install peer dependencies yourself. npm WARN [email protected] requires a peer of eslint-plugin-react@^7.11.0 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] install: detect-libc prebuild-install || node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\zuhair\AppData\Roaming\npm-cache_logs\2019-04-24T21_41_32_370Z-debug.log

Describe the bug The Timestamp to Dateconversion for objects behaves differently for newly created products and existing products that are converted viaconvertObjectTimestampPropertiesToDateingeneric-db.js`.

The crucial parts in generic-db.js are: create method sets createTimestamp and updateTimestamp directly to a Date:

...
return {
      id: docId,
      ...data,
      createTimestamp: new Date(), <<<<<< Type is Date
      updateTimestamp: new Date() <<<<<< Type is Date
    }

...whereas read and readAll methods use convertObjectTimestampPropertiesToDate to convert the timestamps from Firestore to Dates. But the issue is that in convertObjectTimestampPropertiesToDate, existing properties are not replaced but a new newObj object is added with the converted values.

return {
      ...obj,
      newObj
    }

So in the end, a loaded product from the database looks like this:

product: {
  ...,
  createTimestamp <<< Timestamp
  updateTimestamp <<< Timestamp
  newObj: {
    createTimestamp <<< Date
    updateTimestamp <<< Date
  }
}

To Reproduce Steps to reproduce the behavior:

1. Load Products page
2. Set breakpoint in the browser to investigate objects

Expected behavior Objects have the same properties with the same types when being loaded from the DB or returned from the create method.

Describe the bug Running npm run setup error with a bunch of the errors below

npm WARN tar ENOENT: no such file or directory, open 'C:\Users\hcmlo\Documents\Work\projects\textloop\node_modules\.staging\@types\lodash-b2c07a52\ts3.1\fp\zipWith.d.ts'

Here are the 2 logs output.

2019-12-02T15_21_44_116Z-debug.log 2019-12-02T15_21_04_245Z-debug.log

running npm install and then npm run setup will complete the install. At this point npx will no longer work and error out when npx firebase login

internal/modules/cjs/loader.js:305
      throw err;
      ^

Error: Cannot find module 'C:\Users\hcmlo\AppData\Roaming\npm\node_modules\npx\node_modules\libnpx\index.js'. Please verify that the package.json has a valid 
"main" entry
    at tryPackage (internal/modules/cjs/loader.js:297:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:528:18)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:784:27)
    at Function.Module._load (internal/modules/cjs/loader.js:690:27)
    at Module.require (internal/modules/cjs/loader.js:852:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (C:\Users\hcmlo\AppData\Roaming\npm\node_modules\npx\index.js:3:13)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32) {
  code: 'MODULE_NOT_FOUND',
  path: 'C:\\Users\\hcmlo\\AppData\\Roaming\\npm\\node_modules\\npx\\node_modules\\libnpx\\package.json',
  requestPath: 'libnpx'
}

Lighthouse integration to CI.

• Minimum score requirements can be found in package.json , they can be configured manually.
• Budget can be found in ci-scripts/budget.json, as per Google documentation (default value are from here : https://developers.google.com/web/tools/lighthouse/audits/budgets)
• This adds a last step in circle ci, after deployment. It won't cancel/revert deployment if the audit doesn't pass.
• Unfortunately, Google doesn't have an official Docker image for lighthouse + node, so I found another one on docker hub

Describe the bug Can't finalize CI/CD setup. Jobs failed with this error message : npm run lint npm info it worked if it ends with ok npm info using [email protected] npm info using [email protected] npm info lifecycle [email protected]~prelint: [email protected] npm info lifecycle [email protected]~lint: [email protected]

[email protected] lint /home/circleci/repo vue-cli-service lint

ERROR You are using Node v7.10.1, but vue-cli-service requires Node >=8. Please upgrade your Node version.

I don't understand why it's saying that i'm using Node v7.10.1. As on my laptop i have version 10 install. I have even change the version in package.json to "engines": { "npm": ">=6.4.0", "node": ">=10.5.0" },

Firebase is vendor lock-in. It is not OSS.

Describe the solution you'd like As parse server project is indeed OSS and fully maintained, wouldn't make sense to deploy ins a Parse server instance?

Additional context My startup is based on Parse server and it provides ~95% of the same features. I'm not a developer so i cannot measure the complexity of this feature.

The login method is badly written, everytime you login, it reads the database to check if the user has its own collection or not.

I am talking about this file

authentication.actions.js

Here is how i fixed it for me

login: async ({ commit, dispatch }, firebaseAuthUser) => {
// ##########  ctime is the account creation timestamp. stime is the last login timestamp ########
    const ctime = firebaseAuthUser.metadata.a
    const stime = firebaseAuthUser.metadata.b
    let user

    // ##########  CHECK IF THE USER LOGGED IN FOR THE FIRST TIME ########
    if (ctime === stime){
      user = await createNewUserFromFirebaseAuthUser(firebaseAuthUser)
    } else {
           const authuser = firebaseAuthUser.providerData[0]
            user = {displayName:authuser.displayName , id: firebaseAuthUser.uid, email:authuser.email, photoURL:authuser.photoURL, created:ctime , lastLogin:stime}
    }

    commit('setUser', user)
    dispatch('products/getUserProducts', null, { root: true })
  }

No more useless reads , and it's faster. If someone can put a pull request for this because i didn't fork the repo