palashmon/learn-node-pm

Learning to build applications and APIs with @wesbos

Learn Node

These are the starter files to accompany the LearnNode.com course. I keep updating this repo on regular basis after thorough understanding, practicing & re-learning each module in this course.

Sample Data

To load sample data, run the following command in your terminal:

npm run sample

If you have previously loaded in this data, you can wipe your database 100% clean with:

npm run blowitallaway

That will populate 16 stores with 3 authors and 41 reviews. The logins for the authors are as follows:

Name	Email (login)	Password
Wes Bos	[email protected]	wes
Debbie Downer	[email protected]	debbie
Beau	[email protected]	beau

learn-node-pm's Issues

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of dompurify is breaking the build 🚨

Version 1.1.0 of dompurify was just published.

Branch	Build failing 🚨
Dependency	dompurify
Current Version	1.0.2
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

dompurify is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of autoprefixer is breaking the build 🚨

Version 8.6.3 of autoprefixer was just published.

Branch	Build failing 🚨
Dependency	[autoprefixer](https://github.com/postcss/autoprefixer)
Current Version	8.6.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

autoprefixer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

8.6.3

• Add warnings for unsupported Grid features.
• Add warnings about wrong Grid properties.
• Add note about grid option for grid properties in autoprefixer --info.

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Update webpack to the latest version 3.5.2

Version 3.5.2 of webpack just got published.

Dependency	webpack
Current Version	3.4.1
Type	devDependency

There might be a bunch of new features, fixes and perf improvements that might help us.
Let us look into these changes and try to get onto the latest version of webpack.

Fix gravatar fallback image

Fix gravatar fallback image for logged in user. It is not showing the retro image:

Currently it is showing the default one:

Update extract-text-webpack-plugin to 3.0.0

Update extract-text-webpack-plugin to 3.0.0

# For webpack 3
npm i -D extract-text-webpack-plugin

# For webpack 2
npm i -D [email protected]

# For webpack 1
npm i -D [email protected]

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Update webpack to the latest version 3.4.0

Version 3.4.0 of webpack just got published.

Dependency	webpack
Current Version	2.2.1
Type	devDependency

There might be a bunch of new features, fixes and perf improvements that might help us.
Let us look into these changes and try to get onto the latest version of webpack.