Bug: Deploy to Heroku Postgres Issue

[vcao]

Describe the bug
The Postgres image that Spoke is trying to use on Heroku is depcreated when using deploy to production or quick start. The message reads:
We tried to create heroku-postgresql:basic, but received an error from the add-on provider. Try the request again, or log a support ticket and include this message: The basic plan has reached end-of-life. You can try again with a valid plan. See the available plans with: heroku addons:plans heroku-postgresql.

To Reproduce
Steps to reproduce the behavior:

1. Go to Spoke README: https://github.com/StateVoicesNational/Spoke
2. Click on Deploy to Heroku
3. Fill in all required environmental variables
4. See error: "App creation failed." "The basic plan has reached end-of-life."

Expected behavior
A starter or production ready Spoke deployment.

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

Platform (please complete the following information):

• Spoke Version: 14.1.1
• Heroku

[vcao]

I believe the app.json file would need to be updated with the right Heroku Postgres plan for the quick start plan. So either essential or standard, since basic is longer available. Redis also needs to be configured to heroku-redis:mini

[engelhartrueben]

Hi @vcao. State Voices doesn't use Heroku, so it is great help to get feedback.

I see that you have your own branch of Dispatch and have made some minor changes to your app.json file. Did that resolve your issue? If so, we would welcome a pull request! Otherwise, I can spend some time on this.

[vcao]

Thank you for that update. I attempted fixing the app.json file with the appropriate Heroku add-ons, but it won't deploy. I deployed the MoveOn.org version of Spoke about two years ago. I would appreciate any pointers to get it deployed on Heroku again.

Build log:

=== Fetching app code
=== Building web (Dockerfile)
Sending build context to Docker daemon  8.075MBStep 1/17 : ARG BUILDER_IMAGE=node:20.11.1
Step 2/17 : ARG RUNTIME_IMAGE=node:20.11.1-alpine
Step 3/17 : ARG PHONE_NUMBER_COUNTRY=US
Step 4/17 : FROM ${BUILDER_IMAGE} as builder
20.11.1: Pulling from library/node
71215d55680c: Pulling fs layer
3cb8f9c23302: Pulling fs layer
5f899db30843: Pulling fs layer
567db630df8d: Pulling fs layer
f4ac4e9f5ffb: Pulling fs layer
5be7f83aa483: Pulling fs layer
ff4370aa4380: Pulling fs layer
5b2515aa9c66: Pulling fs layer
567db630df8d: Waiting
5be7f83aa483: Waiting
ff4370aa4380: Waiting
f4ac4e9f5ffb: Waiting
5b2515aa9c66: Waiting
3cb8f9c23302: Verifying Checksum
3cb8f9c23302: Download complete
71215d55680c: Verifying Checksum
71215d55680c: Download complete
5f899db30843: Verifying Checksum
5f899db30843: Download complete
f4ac4e9f5ffb: Verifying Checksum
f4ac4e9f5ffb: Download complete
ff4370aa4380: Verifying Checksum
ff4370aa4380: Download complete
5b2515aa9c66: Verifying Checksum
5b2515aa9c66: Download complete
5be7f83aa483: Verifying Checksum
5be7f83aa483: Download complete
567db630df8d: Verifying Checksum
567db630df8d: Download complete
71215d55680c: Pull complete
3cb8f9c23302: Pull complete
5f899db30843: Pull complete
567db630df8d: Pull complete
f4ac4e9f5ffb: Pull complete
5be7f83aa483: Pull complete
ff4370aa4380: Pull complete
5b2515aa9c66: Pull complete
Digest: sha256:e06aae17c40c7a6b5296ca6f942a02e6737ae61bbbf3e2158624bb0f887991b5
Status: Downloaded newer image for node:20.11.1
 ---> 2e805f601f2b
Step 5/17 : ENV NODE_ENV=production     OUTPUT_DIR=./build     ASSETS_DIR=./build/client/assets     ASSETS_MAP_FILE=assets.json     PHONE_NUMBER_COUNTRY=${PHONE_NUMBER_COUNTRY}
 ---> Running in d097be584934
Removing intermediate container d097be584934
 ---> ca64ff2bceb5
Step 6/17 : COPY . /spoke
 ---> 882eb2326616
Step 7/17 : WORKDIR /spoke
 ---> Running in 3fe62cd48c27
Removing intermediate container 3fe62cd48c27
 ---> 2a2137c1ba9f
Step 8/17 : RUN yarn install --ignore-scripts --non-interactive --frozen-lockfile &&     yarn run prod-build &&     rm -rf node_modules &&     yarn install --production --ignore-scripts
 ---> Running in c1db71797292
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Resolution field "axios@0.28.0" is incompatible with requested version "axios@^1.6.7"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^7.0.1"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^7.0.1"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^7.0.1"
warning Resolution field "axios@0.28.0" is incompatible with requested version "axios@^1.6.2"
warning Resolution field "axios@0.28.0" is incompatible with requested version "axios@^1.6.0"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^3.0.0"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^3.0.1"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^3.0.0"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^4.0.0"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^4.0.0"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^7.0.1"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^7.0.1"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^3.0.1"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^5.2.0"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^5.1.0"
warning Resolution field "strip-ansi@6.0.1" is incompatible with requested version "strip-ansi@^5.0.0"
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning "react-scripts > jest-watch-typeahead@1.1.0" has incorrect peer dependency "jest@^27.0.0 || ^28.0.0".
warning "react-formal > @typescript-eslint/parser@4.33.0" has incorrect peer dependency "eslint@^5.0.0 || ^6.0.0 || ^7.0.0".
warning Workspaces can only be enabled in private projects.
[5/5] Building fresh packages...
warning Ignored scripts due to flag.
Done in 73.28s.
yarn run v1.22.19
$ npm run clean && npm run prod-build-client && npm run prod-build-server
> spoke@14.1.1 clean
> rm -rf $OUTPUT_DIR
> spoke@14.1.1 prod-build-client
> webpack --config ./webpack/config.js
Configuring Webpack with {
  assetsDir: './build/client/assets',
  assetMapFile: 'assets.json',
  outputFile: '[name].[fullhash].js'
}
assets by status 8.8 MiB [cached] 2 assets
orphan modules 2.23 MiB [orphan] 631 modules
runtime modules 1.28 KiB 7 modules
modules by path ./node_modules/ 12.4 MiB
  javascript modules 11.5 MiB 2930 modules
  json modules 991 KiB
    modules by path ./node_modules/browserify-sign/ 2.23 KiB 2 modules
    + 6 modules
modules by path ./src/ 1.38 MiB
  cacheable modules 1.38 MiB 59 modules
  ./src/extensions/service-managers/ sync ^\.\/.*\/react\-component\.js$ 385 bytes [optional] [built] [code generated]
  ./src/extensions/texter-sideboxes/ sync ^\.\/.*\/react\-component\.js$ 725 bytes [optional] [built] [code generated]
  ./src/extensions/service-vendors/ sync ^\.\/.*\/react\-component\.js$ 227 bytes [optional] [built] [code generated]
  ./src/extensions/contact-loaders/ sync ^\.\/.*\/react\-component\.js$ 482 bytes [optional] [built] [code generated]
  ./src/extensions/secret-manager/ sync ^\.\/.*\/index\.js$ 191 bytes [optional] [built] [code generated]
+ 13 modules
ERROR in ./node_modules/asn1.js/lib/asn1/base/buffer.js 3:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/asn1.js/lib/asn1/base'
Did you mean './buffer'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/asn1.js/lib/asn1/base/index.js 4:21-54 5:21-54
 @ ./node_modules/asn1.js/lib/asn1.js 6:12-34
 @ ./node_modules/parse-asn1/asn1.js 6:11-29
 @ ./node_modules/parse-asn1/index.js 3:11-28
 @ ./node_modules/public-encrypt/publicEncrypt.js 1:16-37
 @ ./node_modules/public-encrypt/browser.js 1:0-50
 @ ./node_modules/crypto-browserify/index.js 48:20-45
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/asn1.js/lib/asn1/decoders/pem.js 2:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/asn1.js/lib/asn1/decoders'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/asn1.js/lib/asn1/decoders/index.js 4:15-31
 @ ./node_modules/asn1.js/lib/asn1.js 8:16-42
 @ ./node_modules/parse-asn1/asn1.js 6:11-29
 @ ./node_modules/parse-asn1/index.js 3:11-28
 @ ./node_modules/public-encrypt/publicEncrypt.js 1:16-37
 @ ./node_modules/public-encrypt/browser.js 1:0-50
 @ ./node_modules/crypto-browserify/index.js 48:20-45
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/asn1.js/lib/asn1/encoders/der.js 2:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/asn1.js/lib/asn1/encoders'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/asn1.js/lib/asn1/encoders/index.js 3:15-31
 @ ./node_modules/asn1.js/lib/asn1.js 9:16-42
 @ ./node_modules/parse-asn1/asn1.js 6:11-29
 @ ./node_modules/parse-asn1/index.js 3:11-28
 @ ./node_modules/public-encrypt/publicEncrypt.js 1:16-37
 @ ./node_modules/public-encrypt/browser.js 1:0-50
 @ ./node_modules/crypto-browserify/index.js 48:20-45
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/browserify-zlib/lib/index.js 3:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/browserify-zlib/lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./src/lib/gzip.js 1:0-24 4:4-13 15:4-15
 @ ./src/lib/index.js 12:0-38 12:0-38 12:0-38
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/core-util-is/lib/util.js 103:0-52
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/core-util-is/lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/readable-stream/lib/_stream_readable.js 67:25-48
 @ ./node_modules/readable-stream/readable-browser.js 1:10-63
 @ ./node_modules/browserify-sign/browser/index.js 5:13-39
 @ ./node_modules/crypto-browserify/index.js 39:11-37
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/md5.js/node_modules/readable-stream/lib/_stream_readable.js 43:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/md5.js/node_modules/readable-stream/lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/md5.js/node_modules/readable-stream/readable-browser.js 1:10-63
 @ ./node_modules/md5.js/node_modules/hash-base/index.js 3:16-52
 @ ./node_modules/md5.js/index.js 3:15-35
 @ ./node_modules/create-hash/browser.js 3:10-27
 @ ./node_modules/crypto-browserify/index.js 4:21-58
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/md5.js/node_modules/readable-stream/lib/_stream_writable.js 66:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/md5.js/node_modules/readable-stream/lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/md5.js/node_modules/readable-stream/readable-browser.js 4:0-55
 @ ./node_modules/md5.js/node_modules/hash-base/index.js 3:16-52
 @ ./node_modules/md5.js/index.js 3:15-35
 @ ./node_modules/create-hash/browser.js 3:10-27
 @ ./node_modules/crypto-browserify/index.js 4:21-58
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/md5.js/node_modules/readable-stream/lib/internal/streams/buffer_list.js 11:15-32
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/md5.js/node_modules/readable-stream/lib/internal/streams'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/md5.js/node_modules/readable-stream/lib/_stream_readable.js 62:17-58
 @ ./node_modules/md5.js/node_modules/readable-stream/readable-browser.js 1:10-63
 @ ./node_modules/md5.js/node_modules/hash-base/index.js 3:16-52
 @ ./node_modules/md5.js/index.js 3:15-35
 @ ./node_modules/create-hash/browser.js 3:10-27
 @ ./node_modules/crypto-browserify/index.js 4:21-58
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/readable-stream/node_modules/safe-buffer/index.js 2:13-30
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/readable-stream/node_modules/safe-buffer'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/readable-stream/lib/_stream_readable.js 55:13-42
 @ ./node_modules/readable-stream/readable-browser.js 1:10-63
 @ ./node_modules/browserify-sign/browser/index.js 5:13-39
 @ ./node_modules/crypto-browserify/index.js 39:11-37
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/ripemd160/index.js 2:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/ripemd160'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/create-hmac/browser.js 7:16-36
 @ ./node_modules/crypto-browserify/index.js 5:21-58
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/ripemd160/node_modules/readable-stream/lib/_stream_readable.js 43:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/ripemd160/node_modules/readable-stream/lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/ripemd160/node_modules/readable-stream/readable-browser.js 1:10-63
 @ ./node_modules/ripemd160/node_modules/hash-base/index.js 3:16-52
 @ ./node_modules/ripemd160/index.js 4:15-35
 @ ./node_modules/create-hmac/browser.js 7:16-36
 @ ./node_modules/crypto-browserify/index.js 5:21-58
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/ripemd160/node_modules/readable-stream/lib/_stream_writable.js 66:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/ripemd160/node_modules/readable-stream/lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/ripemd160/node_modules/readable-stream/readable-browser.js 4:0-55
 @ ./node_modules/ripemd160/node_modules/hash-base/index.js 3:16-52
 @ ./node_modules/ripemd160/index.js 4:15-35
 @ ./node_modules/create-hmac/browser.js 7:16-36
 @ ./node_modules/crypto-browserify/index.js 5:21-58
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/ripemd160/node_modules/readable-stream/lib/internal/streams/buffer_list.js 11:15-32
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/ripemd160/node_modules/readable-stream/lib/internal/streams'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/ripemd160/node_modules/readable-stream/lib/_stream_readable.js 62:17-58
 @ ./node_modules/ripemd160/node_modules/readable-stream/readable-browser.js 1:10-63
 @ ./node_modules/ripemd160/node_modules/hash-base/index.js 3:16-52
 @ ./node_modules/ripemd160/index.js 4:15-35
 @ ./node_modules/create-hmac/browser.js 7:16-36
 @ ./node_modules/crypto-browserify/index.js 5:21-58
 @ ./src/extensions/secret-manager/crypto.js 9:13-41
 @ ./src/extensions/secret-manager/index.js 3:0-44 31:43-59
 @ ./src/server/api/lib/config.js 4:0-63 69:17-26
 @ ./src/lib/timezones.js 5:0-53 69:40-49
 @ ./src/lib/index.js
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/safe-buffer/index.js 3:13-30
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/safe-buffer'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/string_decoder/lib/string_decoder.js 26:13-42
 @ ./node_modules/stream-browserify/node_modules/readable-stream/lib/_stream_readable.js 158:40-80 301:38-78
 @ ./node_modules/stream-browserify/index.js 28:18-68
 @ ./node_modules/browserify-zlib/lib/index.js 4:16-43
 @ ./src/lib/gzip.js 1:0-24 4:4-13 15:4-15
 @ ./src/lib/index.js 12:0-38 12:0-38 12:0-38
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/stream-browserify/node_modules/readable-stream/lib/_stream_readable.js 43:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/stream-browserify/node_modules/readable-stream/lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/stream-browserify/index.js 28:18-68
 @ ./node_modules/browserify-zlib/lib/index.js 4:16-43
 @ ./src/lib/gzip.js 1:0-24 4:4-13 15:4-15
 @ ./src/lib/index.js 12:0-38 12:0-38 12:0-38
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/stream-browserify/node_modules/readable-stream/lib/_stream_writable.js 66:13-37
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/stream-browserify/node_modules/readable-stream/lib'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/stream-browserify/index.js 29:18-68
 @ ./node_modules/browserify-zlib/lib/index.js 4:16-43
 @ ./src/lib/gzip.js 1:0-24 4:4-13 15:4-15
 @ ./src/lib/index.js 12:0-38 12:0-38 12:0-38
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
ERROR in ./node_modules/stream-browserify/node_modules/readable-stream/lib/internal/streams/buffer_list.js 11:15-32
Module not found: Error: Can't resolve 'buffer' in '/spoke/node_modules/stream-browserify/node_modules/readable-stream/lib/internal/streams'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "buffer": require.resolve("buffer/") }'
	- install 'buffer'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "buffer": false }
 @ ./node_modules/stream-browserify/node_modules/readable-stream/lib/_stream_readable.js 62:17-58
 @ ./node_modules/stream-browserify/index.js 28:18-68
 @ ./node_modules/browserify-zlib/lib/index.js 4:16-43
 @ ./src/lib/gzip.js 1:0-24 4:4-13 15:4-15
 @ ./src/lib/index.js 12:0-38 12:0-38 12:0-38
 @ ./src/client/error-catcher.js
 @ ./src/client/index.jsx 5:0-43 11:2-14 14:2-14
17 errors have detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.
webpack 5.92.1 compiled with 17 errors in 43854 ms
npm notice 
npm notice New minor version of npm available! 10.2.4 -> 10.9.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.9.0>
npm notice Run `npm install -g npm@10.9.0` to update!
npm notice 
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
The command '/bin/sh -c yarn install --ignore-scripts --non-interactive --frozen-lockfile &&     yarn run prod-build &&     rm -rf node_modules &&     yarn install --production --ignore-scripts' returned a non-zero code: 1

[engelhartrueben]

#2493 fixes docker image; will look into fixing Heroku plans tomorrow.
Expect a patch release Monday (10/21) that will include this + some other bug fixes.

[engelhartrueben]

@vcao we are still shooting for a 10/21 patch, but if you need this up and running sooner, add:

• "buffer": "^6.0.3", on line 122 in package.json
• In app.json line 186, change "heroku-postgresql:basic", to "heroku-postgresql:essential-0",

These two changes fixes the updated plans for Heroku and the Docker image.
Regardless, please keep me posted on the success (or lack there of) of you Heroku deployment. Happy to help where I can.
Thanks

[bryan-graham]

@engelhartrueben with your changes and a yarn.lock update, I was able to deploy 14.1.1 to Heroku. Thanks!