Version 4.11.1 of @types/express was just published.

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

@types/express 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.

Your Greenkeeper Bot 🌴

We need students to generate their own web push key. Having a shared key is bad

The support given for installing this is not helping
first: the tutorial mentions a file : server/cli/cli.js which doesn't exist ??? ( which branch should we choose in order to follow your tutorials properly ? some branches have a server/cli folder, some don't ?

After installing all dependencies with Yarn, I installed the certificates ( thanks for mentioning to win 10 users they have to get openSSL in their path ?), everything finally went well, I then ran "npm run watch" and there's some error in js mentinoning there's no API and UI, at the end of the day I went to learn about service workers and I finally wasted my time with little to no support to install your project. So I'm stuck what do I do now ?

So could you please give some recommendation for windows 10 users ( like me ) to install your app with clear instructions, the ones you gave either on FEM or on your readme don't work, for instance why do I always stumble upon errors in javascript files preventing me to launch the app in any cases ?

Version 1.1.7 of file-loader was just published.

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

file-loader 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.

Your Greenkeeper Bot 🌴

Version 1.14.12 of nodemon was just published.

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

nodemon 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.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.1.0 of idb was just published.

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

idb 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.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.21.1 of webpack-hot-middleware was just published.

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

webpack-hot-middleware 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.

Your Greenkeeper Bot 🌴

Version 16.0.35 of @types/react was just published.

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

@types/react 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.

Your Greenkeeper Bot 🌴

npm fails when its renaming a file inside node_modules.
I think its this files - /node_modules/concurrently/src/main.js.3376272737
I am running this on Bash in a windows 10.

Version 3.11.0 of webpack was just published.

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

webpack 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.

Your Greenkeeper Bot 🌴

Version 0.9.36 of muicss was just published.

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

muicss 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.

Your Greenkeeper Bot 🌴

I wasn't familiar with git lfs and had to troubleshoot git clone.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 3.3.0 of web-push was just published.

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

web-push 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.

Your Greenkeeper Bot 🌴

Main point - if node upgrade is performed, sass native bindings must be rebuilt

• "search.exclude": { "dist/**/*": true

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.21.0 of moment was just published.

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

moment 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.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 7.1.3 of babel-loader was just published.

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

babel-loader 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.

Your Greenkeeper Bot 🌴

Version 21.7.0 of eslint-plugin-jest was just published.

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

eslint-plugin-jest 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.

Your Greenkeeper Bot 🌴

In case the setup scripts do not work, there should be manual instructions for setting up certs, VAPID keys, etc...

I am working on Challenge One Solution from the FEM course and am trying to run the production build but the commands shown seem to have changed. The run script is no longer valid as indicated by the message.

So when I run a production build with npm run build:prod

And then try to serve it with serve dist/ -T, the server starts up on https://localhost:5000 but the build does not run.

Instead, I get the error: Uncaught Error: [HMR] Hot Module Replacement is disabled.

Here is what my browser console looks like:

Do I need to disable module hot reloading somehow?

Version 1.1.4 of compression-webpack-plugin was just published.

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

compression-webpack-plugin 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.

Your Greenkeeper Bot 🌴

Version 4.27.3 of @types/sequelize was just published.

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

@types/sequelize 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.

Your Greenkeeper Bot 🌴

Version 4.32.0 of sequelize was just published.

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

sequelize 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.

/**
 * Current behaviour
 */
const created = await Model.upsert(....values....);
/**

 * New feature

 */
// with options.returning = false / undefined

const created = await Model.upsert(....values...., { returning: false });
// with options.returning = true

const [record, created] = await Model.upsert(....values...., { returning: true });

Your Greenkeeper Bot 🌴

Version 2.11.1 of webpack-dev-server was just published.

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

webpack-dev-server 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.

Your Greenkeeper Bot 🌴

Hi! First of all, thanks for taking the effort to prepare this course! This is something that I've been looking for and it's great to have both high-level overview of PWAs and practical examples gathered and explained in one place :)

Unfortunately I'm currently stuck trying to get HTTPS certificate to work.
I think I screwed something up during the installation.
I was just going along the instructions in README and ran

npm run prepcerts

At that point I didn't expect that popup in Firefox asking for some permissions, so I decided to skip them for the time being (left all the checkboxes unchecked) and come back and change them later.

Later I checked that I had devcert Authority under "Certifiacates / Authorities" tab, but all the browsers considered the page "Not secure". So, apart from silly warnings, I was also unable to run Lighthouse tests.

Finally I tried to do fresh reinstall - I cloned the repository, deleted devcert authority from Firefox settings and tried to generate the certifacte again. Unfortunately, it seems that I can generate local keys, but I can't get the Firefox prompt to show up and create the certifiacte for me.

I check devcert README (https://github.com/davewasmer/devcert#how-it-works) and what I found is:

When you ask for a development certificate, devcert will first check to see if it has run on this machine before. If not, it will create a root certificate authority and add it to your OS and various browser trust stores. You'll likely see password prompts from your OS at this point to authorize the new root CA. This is the only time you'll see these prompts.

How should I proceed to get this certificate if I've already run it once on my machine?

I spend an hour fighting with the certificates... when I discovered that page:

https://www.chromium.org/blink/serviceworker/service-worker-faq

solution is to start chrome with:

"C:\Program Files (x86)\Google\Chrome Beta\Application\chrome.exe" --allow-insecure-localhost https://localhost

Would highly recommend you suggest using this trick during development... playing with certs on Windows is not pretty... the flag allow me to use service worker, fetch, push notifications!

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 6.0.7 of sass-loader was just published.

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

sass-loader 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.

Your Greenkeeper Bot 🌴

The text on this slide says to add the worker import to App.jsx. However, based on this commit from the femasters-3-complete branch, this is wrong, and it should be added to client/index.js. ( I spent a few hours debugging why my web server wouldn't start when I had it added to App.jsx)

(I attended Steve's talk at Develop Denver and finally got around to checking this out. Thanks for having it available 😀 )

Version 2.10.0 of webpack-bundle-analyzer was just published.

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

webpack-bundle-analyzer 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.

Your Greenkeeper Bot 🌴

Version 3.4.7 of style-ext-html-webpack-plugin was just published.

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

style-ext-html-webpack-plugin 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.

Your Greenkeeper Bot 🌴

Version 8.2.2 of babel-eslint was just published.

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

babel-eslint 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.

Your Greenkeeper Bot 🌴

Version 4.16.0 of eslint was just published.

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

eslint 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.

Your Greenkeeper Bot 🌴

Version 1.13.0 of greenkeeper-lockfile was just published.

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

greenkeeper-lockfile 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.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.1.1 of worker-loader was just published.

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

worker-loader 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.

Your Greenkeeper Bot 🌴

Version 7.6.0 of eslint-plugin-react was just published.

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

eslint-plugin-react 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.

Your Greenkeeper Bot 🌴

Version 2.3.1 of chalk was just published.

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

chalk 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.

Your Greenkeeper Bot 🌴

Version 16.0.4 of @types/react-dom was just published.

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

@types/react-dom 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.

Your Greenkeeper Bot 🌴

On the android simulator, the data is not loaded because the endpoint it is trying to hit is https://localhost:3100, which as you indicated, does not work on the simulator.

How do I fix this?

Make it clear that CORS mode is needed for fetching the fallback image

• comment out webpack plugin
• app.css should be added to whitelist for precaching

Version 0.28.9 of css-loader was just published.

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

css-loader 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.

Your Greenkeeper Bot 🌴

• Improper CORS headers on document request (never complete the navigation event)

Version 2.0.5 of webpack-dev-middleware was just published.

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

webpack-dev-middleware 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.

Your Greenkeeper Bot 🌴

🚨 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.

Getting this error for all of the build commands:

ERROR in StyleExtHtmlWebpackPluginError: StyleExtHtmlWebpackPlugin: could not find Extr actTextWebpackPlugin's generated .css file; available files: './apple-touch-ic on-114x114.png,./apple-touch-icon-120x120.png,./apple-touch-icon-144x144.png,. /apple-touch-icon-152x152.png,./apple-touch-icon-180x180.png,./apple-touch-ico n-57x57.png,./apple-touch-icon-60x60.png,./apple-touch-icon-72x72.png,./apple- touch-icon-76x76.png,./img/launcher-icon-1x.png,./img/launcher-icon-2x.png,./i mg/launcher-icon-4x.png,app-4617fcb7479739423ea1.js,app-4617fcb7479739423ea1.j s.map'

Went through the entire setup process as described in the Readme

Ed: Works fine when I comment out

plugins.push(new StyleExtHtmlWebpackPlugin()); // at line 70, webpack/plugins/config.js

Found some issues with people using node 8.x. Rather than demand a 7.x release for this course, 8.x should be supported