Error Deploying to Vercel

mhigley · 19 June 2020 01:27

Running through a simple tutorial (https://dev.to/frontity/building-a-blog-using-frontity-and-wordpress-8oc) and completely unable to deploy to Vercel. The only error I’m getting is:

Something went wrong with the build. Please run npx frontity dev --production locally to find out.

I skipped the tutorial deployment instructions (the official docs were slightly more verbose) and removed all the parts related to Disqus thinking that I had an error somewhere in that code and yet it continues to be problematic. I’ve run the command as prompted but it shows no errors.

Any thoughts?

18:09:26.565 Retrieving list of deployment files…
18:09:27.767 Downloading 65 deployment files…
18:09:31.319 Installing build runtime…
18:09:32.828 Build runtime installed: 1508.908ms
18:09:33.144 Looking up build cache…
18:09:33.177 Build cache not found
18:09:33.500 Downloading user files…
18:09:44.558 > core-js@2.6.11 postinstall /vercel/39630efe/node_modules/babel-polyfill/node_modules/core-js
18:09:44.558 > node -e “try{require(’./postinstall’)}catch(e){}”
18:09:44.615 e[96mThank you for using core-js (e[94m https://github.com/zloirock/core-js e[96m) for polyfilling JavaScript standard library!e[0m
18:09:44.615 e[96mThe project needs your help! Please consider supporting of core-js on Open Collective or Patreon: e[0m
18:09:44.615 e[96m>e[94m https://opencollective.com/core-js e[0m
18:09:44.615 e[96m>e[94m https://www.patreon.com/zloirock e[0m
18:09:44.615 e[96mAlso, the author of core-js (e[94m https://github.com/zloirock e[96m) is looking for a good job -)e[0m
18:09:44.619 > core-js@2.6.11 postinstall /vercel/39630efe/node_modules/babel-runtime/node_modules/core-js
18:09:44.619 > node -e “try{require(’./postinstall’)}catch(e){}”
18:09:44.675 > core-js@3.6.5 postinstall /vercel/39630efe/node_modules/core-js
18:09:44.675 > node -e “try{require(’./postinstall’)}catch(e){}”
18:09:44.728 > ejs@2.7.4 postinstall /vercel/39630efe/node_modules/ejs
18:09:44.728 > node ./postinstall.js
18:09:44.776 Thank you for installing e[35mEJSe[0m: built with the e[32mJakee[0m JavaScript build tool (e[32mhttps://jakejs.com/e[0m)
18:09:45.285 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
18:09:45.285 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
18:09:45.285 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
18:09:45.285 npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
18:09:45.287 added 821 packages from 466 contributors in 10.537s
18:09:45.597 20 packages are looking for funding
18:09:45.597 run npm fund for details
18:09:45.623 Running “build” script in “package.json”
18:09:45.624 Running “npm run build”
18:09:45.808 > frontity-demo@1.0.0 build /vercel/39630efe
18:09:45.808 > frontity build
18:09:46.545 mode: production
18:09:46.612 Building es5 bundle
18:09:58.222 Building module bundle
18:10:04.114 Building server bundle
18:10:13.370 Error: Something went wrong with the build. Please run npx frontity dev --production locally to find out.
18:10:13.370 at Object.build (/vercel/79647f38b6c2ea21/.build-utils/.builder/node_modules/@frontity/now/dist/index.js:83:19)
18:10:13.370 at async buildStep (/var/task/sandbox-worker.js:20407:20)
18:10:13.370 at async mainSub (/var/task/sandbox-worker.js:20144:9)
18:10:13.370 at async main (/var/task/sandbox-worker.js:20024:5)
18:10:14.255 [dmesg] follows:
18:10:14.255 [ 1960.485129] ecs-bridge: port 1(vethc1bfb296) entered disabled state
18:10:14.255 [ 1960.489617] device vethc1bfb296 entered promiscuous mode
18:10:14.255 [ 1960.493610] ecs-bridge: port 1(vethc1bfb296) entered blocking state
18:10:14.255 [ 1960.498006] ecs-bridge: port 1(vethc1bfb296) entered forwarding state
18:10:15.046 Done with “package.json”

System:

OS: macOS 10.15.5
CPU: (12) x64 Intel® Core™ i7-8850H CPU @ 2.60GHz
Memory: 61.77 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh

Binaries:

Node: 13.12.0 - /usr/local/bin/node
npm: 6.14.4 - /usr/local/bin/npm

Browsers:

Chrome: 83.0.4103.106
Edge: Not Found
Firefox: Not Found
Safari: 13.1.1

npmPackages:

@frontity/core: ^1.7.0 => 1.7.0
@frontity/html2react: ^1.3.3 => 1.3.3
@frontity/mars-theme: ./packages/mars-theme => 1.4.2
@frontity/now: ^1.1.0 => 1.1.0
@frontity/tiny-router: ^1.2.0 => 1.2.0
@frontity/wp-source: ^1.7.1 => 1.7.1
disqus-react: ^1.0.9 => 1.0.9
frontity: ^1.8.0 => 1.8.0

npmGlobalPackages:

frontity: Not Found
npx: Not Found

chris · 19 June 2020 05:24

EDIT: I had a look through the changes since our last deployment, turns out the addition of react-transition-group@4.4.1 was causing the below error, I removed this dependency and deployed first attempt.

Having a similar issue trying to deploy to Now, using the default Frontity now.json file I get your error, using my existing now.json config file I get the below error:

2020-06-19T04:56:08.282Z TypeError: Cannot read property ‘type’ of null
2020-06-19T04:56:08.283Z at /vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:43126:56
2020-06-19T04:56:08.283Z at Array.every ()
2020-06-19T04:56:08.283Z at handleWrappers (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:43126:41)
2020-06-19T04:56:08.283Z at module.exports.module.exports (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:46737:3)
2020-06-19T04:56:08.283Z at Job.emitDependency (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:39845:40)
2020-06-19T04:56:08.283Z at /vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:39631:18
2020-06-19T04:56:08.283Z at Array.map ()
2020-06-19T04:56:08.283Z at Object.module.exports.module.exports [as default] (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:39627:27)
2020-06-19T04:56:08.283Z at compile (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:26391:80)
2020-06-19T04:56:08.283Z at Object.build (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:26524:71)
2020-06-19T04:56:08.565Z [dmesg] follows:
2020-06-19T04:56:08.565Z [ 2055.387379] ecs-bridge: port 1(veth9972a1bc) entered disabled state
2020-06-19T04:56:08.565Z [ 2055.390165] device veth9972a1bc entered promiscuous mode
2020-06-19T04:56:08.565Z [ 2055.392611] ecs-bridge: port 1(veth9972a1bc) entered blocking state
2020-06-19T04:56:08.565Z [ 2055.396924] ecs-bridge: port 1(veth9972a1bc) entered forwarding state

Build log:

2020-06-19T04:56:06.911Z 11 packages are looking for funding
2020-06-19T04:56:06.911Z run npm fund for details
2020-06-19T04:56:06.911Z
2020-06-19T04:56:08.282Z TypeError: Cannot read property ‘type’ of null
2020-06-19T04:56:08.283Z at /vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:43126:56
2020-06-19T04:56:08.283Z at Array.every ()
2020-06-19T04:56:08.283Z at handleWrappers (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:43126:41)
2020-06-19T04:56:08.283Z at module.exports.module.exports (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:46737:3)
2020-06-19T04:56:08.283Z at Job.emitDependency (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:39845:40)
2020-06-19T04:56:08.283Z at /vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:39631:18
2020-06-19T04:56:08.283Z at Array.map ()
2020-06-19T04:56:08.283Z at Object.module.exports.module.exports [as default] (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:39627:27)
2020-06-19T04:56:08.283Z at compile (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:26391:80)
2020-06-19T04:56:08.283Z at Object.build (/vercel/5fcb12b5810a14f0/.build-utils/.builder/node_modules/@now/node/dist/index.js:26524:71)
2020-06-19T04:56:08.565Z [dmesg] follows:
2020-06-19T04:56:08.565Z [ 2055.387379] ecs-bridge: port 1(veth9972a1bc) entered disabled state
2020-06-19T04:56:08.565Z [ 2055.390165] device veth9972a1bc entered promiscuous mode
2020-06-19T04:56:08.565Z [ 2055.392611] ecs-bridge: port 1(veth9972a1bc) entered blocking state
2020-06-19T04:56:08.565Z [ 2055.396924] ecs-bridge: port 1(veth9972a1bc) entered forwarding state
2020-06-19T04:56:09.064Z Installing build runtime…
2020-06-19T04:56:09.066Z yarn info @now/build-utils@latest…
2020-06-19T04:56:09.071Z yarn info @now/node-server…
2020-06-19T04:56:09.396Z yarn add @now/build-utils@2.4.0, @vercel/build-utils@2.4.0…
2020-06-19T04:56:09.456Z [now] [mutex] process.argv is ["/node12/bin/node","/vercel/.yarn/bin/yarn.js","–prod","–cwd","/vercel/5fba46d2d0ff0898/.build-utils",“add”,"@now/build-utils@2.4.0","@vercel/build-utils@2.4.0"]
2020-06-19T04:56:09.457Z [now] [mutex] process.cwd is “/vercel/5fba46d2d0ff0898/.build-utils”
2020-06-19T04:56:09.457Z [now] [mutex] command is “install”
2020-06-19T04:56:09.457Z [now] [mutex] trying to acquire for 1392
2020-06-19T04:56:09.461Z [now] [mutex] running instance 1392
2020-06-19T04:56:09.608Z yarn add v1.22.4
2020-06-19T04:56:09.623Z info No lockfile found.
2020-06-19T04:56:09.642Z [1/4] Resolving packages…
2020-06-19T04:56:09.797Z [2/4] Fetching packages…
2020-06-19T04:56:09.801Z [3/4] Linking dependencies…
2020-06-19T04:56:09.876Z [4/4] Building fresh packages…
2020-06-19T04:56:09.879Z success Saved lockfile.
2020-06-19T04:56:09.882Z success Saved 2 new dependencies.
2020-06-19T04:56:09.882Z info Direct dependencies
2020-06-19T04:56:09.883Z ├─ @now/build-utils@2.4.0
2020-06-19T04:56:09.883Z └─ @vercel/build-utils@2.4.0
2020-06-19T04:56:09.883Z info All dependencies
2020-06-19T04:56:09.883Z ├─ @now/build-utils@2.4.0
2020-06-19T04:56:09.883Z └─ @vercel/build-utils@2.4.0
2020-06-19T04:56:09.884Z Done in 0.28s.
2020-06-19T04:56:09.899Z yarn add @now/node-server@0.8.2…
2020-06-19T04:56:09.958Z [now] [mutex] process.argv is ["/node12/bin/node","/vercel/.yarn/bin/yarn.js","–prod","–cwd","/vercel/5fba46d2d0ff0898/.build-utils/.builder",“add”,"@now/node-server@0.8.2"]
2020-06-19T04:56:09.958Z [now] [mutex] process.cwd is “/vercel/5fba46d2d0ff0898/.build-utils/.builder”
2020-06-19T04:56:09.958Z [now] [mutex] command is “install”
2020-06-19T04:56:09.958Z [now] [mutex] trying to acquire for 1424
2020-06-19T04:56:09.962Z [now] [mutex] running instance 1424
2020-06-19T04:56:10.112Z yarn add v1.22.4
2020-06-19T04:56:10.128Z info No lockfile found.
2020-06-19T04:56:10.147Z [1/4] Resolving packages…
2020-06-19T04:56:10.263Z warning @now/node-server@0.8.2: This package is no longer maintained. Please use @now/node instead.
2020-06-19T04:56:10.373Z [2/4] Fetching packages…
2020-06-19T04:56:10.788Z [3/4] Linking dependencies…
2020-06-19T04:56:10.881Z [4/4] Building fresh packages…
2020-06-19T04:56:10.884Z success Saved lockfile.
2020-06-19T04:56:10.887Z success Saved 7 new dependencies.
2020-06-19T04:56:10.887Z info Direct dependencies
2020-06-19T04:56:10.888Z └─ @now/node-server@0.8.2
2020-06-19T04:56:10.888Z info All dependencies
2020-06-19T04:56:10.888Z ├─ @now/node-bridge@1.2.2
2020-06-19T04:56:10.888Z ├─ @now/node-server@0.8.2
2020-06-19T04:56:10.888Z ├─ @zeit/ncc@0.18.5
2020-06-19T04:56:10.888Z ├─ fs-extra@7.0.1
2020-06-19T04:56:10.888Z ├─ graceful-fs@4.2.4
2020-06-19T04:56:10.888Z ├─ jsonfile@4.0.0
2020-06-19T04:56:10.888Z └─ universalify@0.1.2
2020-06-19T04:56:10.889Z Done in 0.78s.
2020-06-19T04:56:10.899Z Build runtime installed: 1834.750ms
2020-06-19T04:56:11.241Z Looking up build cache…
2020-06-19T04:56:11.314Z Build cache found. Downloading…
2020-06-19T04:56:13.271Z Build cache downloaded [50.79 MB]: 1955.602ms
2020-06-19T04:56:13.608Z Running package.json builder.exports.build…
2020-06-19T04:56:13.609Z downloading user files…
2020-06-19T04:56:13.609Z installing dependencies for user’s code…
2020-06-19T04:56:17.771Z npm WARN @emotion/styled@10.0.27 requires a peer of @emotion/core@^10.0.27 but none is installed. You must install peer dependencies yourself.
2020-06-19T04:56:17.771Z npm WARN @emotion/styled-base@10.0.27 requires a peer of @emotion/core@^10.0.27 but none is installed. You must install peer dependencies yourself.
2020-06-19T04:56:17.771Z npm WARN bootstrap@4.4.1 requires a peer of jquery@1.9.1 - 3 but none is installed. You must install peer dependencies yourself.
2020-06-19T04:56:17.771Z npm WARN react-addons-css-transition-group@15.6.2 requires a peer of react@^15.4.2 but none is installed. You must install peer dependencies yourself.
2020-06-19T04:56:17.772Z npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/fsevents):
2020-06-19T04:56:17.772Z npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})
2020-06-19T04:56:17.772Z
2020-06-19T04:56:17.772Z up to date in 3.74s
2020-06-19T04:56:18.094Z
2020-06-19T04:56:18.094Z 11 packages are looking for funding
2020-06-19T04:56:18.094Z run npm fund for details
2020-06-19T04:56:18.094Z
2020-06-19T04:56:18.118Z running user script…
2020-06-19T04:56:18.118Z preparing lambda files…
2020-06-19T04:56:18.118Z compiling entrypoint with ncc…
2020-06-19T04:56:18.337Z ncc: Version 0.18.5
2020-06-19T04:56:18.338Z ncc: Compiling file index.js
2020-06-19T04:56:18.599Z Uploading build outputs…
2020-06-19T04:56:20.160Z Build completed. Populating build cache…
2020-06-19T04:56:21.872Z Running package.json builder.exports.prepareCache…
2020-06-19T04:56:32.877Z Uploading build cache [50.79 MB]…
2020-06-19T04:56:33.649Z Build cache uploaded: 771.179ms
2020-06-19T04:56:33.665Z Done with “package.json”
2020-06-19T04:56:33.947Z Done with “build/server.js”

I’ve updated my now.json file to build package.json with @now/node as per one of the warnings and still no dice.

Building the production version and deploying via Frontity works fine, our last deployment was over a month ago and didn’t have any issues.

Not sure how to grab the system, Node and packages like the OP in a quick way but this is also on a Mac with similar specs, using Node 13.9.0 and npm 6.13.7

package.json and now.json available here: https://gist.github.com/twenty/0812513fddef58f7aec7ac222bf887ec

david1 · 6 July 2020 16:28

@mhigley and @chris, any update on this? I’m getting what looks like the same issue:

18:21:08.237  Retrieving list of deployment files...
18:21:09.731  Downloading 72 deployment files...
18:21:16.663  Installing build runtime...
18:21:17.994  Build runtime installed: 1330.933ms
18:21:18.353  Looking up build cache...
18:21:18.396  Build cache not found
18:21:18.761  Downloading user files...
18:21:29.592  > core-js@2.6.11 postinstall /vercel/19e85f29/node_modules/babel-polyfill/node_modules/core-js
18:21:29.592  > node -e "try{require('./postinstall')}catch(e){}"
18:21:29.648  e[96mThank you for using core-js (e[94m https://github.com/zloirock/core-js e[96m) for polyfilling JavaScript standard library!e[0m
18:21:29.648  e[96mThe project needs your help! Please consider supporting of core-js on Open Collective or Patreon: e[0m
18:21:29.648  e[96m>e[94m https://opencollective.com/core-js e[0m
18:21:29.648  e[96m>e[94m https://www.patreon.com/zloirock e[0m
18:21:29.649  e[96mAlso, the author of core-js (e[94m https://github.com/zloirock e[96m) is looking for a good job -)e[0m
18:21:29.653  > core-js@2.6.11 postinstall /vercel/19e85f29/node_modules/babel-runtime/node_modules/core-js
18:21:29.653  > node -e "try{require('./postinstall')}catch(e){}"
18:21:29.709  > core-js@3.6.5 postinstall /vercel/19e85f29/node_modules/core-js
18:21:29.709  > node -e "try{require('./postinstall')}catch(e){}"
18:21:29.760  > ejs@2.7.4 postinstall /vercel/19e85f29/node_modules/ejs
18:21:29.760  > node ./postinstall.js
18:21:29.807  Thank you for installing e[35mEJSe[0m: built with the e[32mJakee[0m JavaScript build tool (e[32mhttps://jakejs.com/e[0m)
18:21:30.330  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
18:21:30.330  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
18:21:30.330  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
18:21:30.331  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
18:21:30.333  added 836 packages from 473 contributors in 10.665s
18:21:30.658  20 packages are looking for funding
18:21:30.658    run `npm fund` for details
18:21:30.686  Running "build" script in "package.json"
18:21:30.686  Running "npm run build"
18:21:30.867  > ljmv-frontity@1.0.0 build /vercel/19e85f29
18:21:30.867  > frontity build
18:21:31.595  mode: production
18:21:31.659  Building es5 bundle
18:21:45.895  Building module bundle
18:21:54.257  Building server bundle
18:22:05.618  Error: Something went wrong with the build. Please run `npx frontity dev --production` locally to find out.
18:22:05.618      at Object.build (/vercel/8a5d30c4e969f9e1/.build-utils/.builder/node_modules/@frontity/now/dist/index.js:84:19)
18:22:05.618      at async buildStep (/var/task/sandbox-worker.js:21041:20)
18:22:05.618      at async mainSub (/var/task/sandbox-worker.js:20778:9)
18:22:05.618      at async main (/var/task/sandbox-worker.js:20648:5)
18:22:07.022  Done with "package.json"

And I tried the whole npx frontity dev --production and that ran without any issues, though it did warn that my package was a bit large (540KB instead of <293KB).

## System:
 - OS: Linux 5.4 Pop!_OS 20.04 LTS
 - CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
 - Memory: 2.32 GB / 31.22 GB
 - Shell: 5.0.16 - /bin/bash
## Binaries:
 - Node: 10.21.0 - ~/n/bin/node
 - npm: 6.14.4 - ~/n/bin/npm
## Browsers:
 - Chrome: 83.0.4103.116
 - Firefox: 78.0.1
## npmPackages:
 - @frontity/core: ^1.7.1 => 1.7.1 
 - @frontity/html2react: ^1.3.4 => 1.3.4 
 - @frontity/tiny-router: ^1.2.1 => 1.2.1 
 - @frontity/wp-source: ^1.8.0 => 1.8.0 
 - frontity: ^1.9.0 => 1.9.0 
 - ljmv-theme: file:packages/ljmv-theme => 1.0.0 
## npmGlobalPackages:
 - frontity: Not Found
 - npx: Not Found

I hadn’t had issues deploying until today and I’m not sure what has changed. Any ideas?

david1 · 8 July 2020 19:41

For the time being, I’ve deployed via a DigitalOcean NodeJS droplet but it really isn’t ideal since deployment now requires SSHing into my droplet and pulling the latest version manually for the time being.

chris · 8 July 2020 22:58

My last error was related from a package I had included since our last deployment. The package in question was:

https://reactcommunity.org/react-transition-group/

It was only something I was playing with, so we didn’t need it, but once removed it deployed to Vercel without any issues.

Debugging was purely trial and error, this was the only major change since our last deployment so was the first area to investigate.

david1 · 10 July 2020 09:56

@chris thanks for clarifying and as a result, I was able to figure out my issue:

Between the fact that you mentioned it was an issue with a package and I thought, “Since I can build locally, perhaps my Node versions are different” and I saw that they were (Vercel defaults to the latest LTS, which is 12.x, and I am using 10.x). So I added "engines": { "node": "10.x" } to my package.json as per this guide and tried again but that didn’t work right away. I do think that this helped…

In reading that guide, they mention that npm install is used over yarn if there is a package-lock.json present. So I deleted my local node_modules folder and package-lock.json file and re-installed everything with npm install. That generated a new package-lock.json, which I committed and pushed to my master branch and it worked!

david1 · 11 July 2020 09:18

I am also working on another project and this happened yet again. I think one thing that’s happening is remove mars-theme so only the theme I create is used. However, I just delete this and it remains in the package-lock.json. I will try not to do this anymore.

I did notice that package dependencies, as in node components that I install in my theme as I’m developing are not transferred to the project’s dependencies until I remove package-lock.json files and re-install. I’m not sure if this is something that should be automated in the build process or not but it’s definitely something developers should be aware of if they experience this issue like I have.

juanma · 13 July 2020 15:54

To “clean” your node_modules and your package-lock.json from dependencies that are not being used in your project you can do…

rm -rf node_modules && rm -rf package-lock.json && rm -rf yarn-error.log && rm -rf yarn.lock && npm cache clean --force

and then do npm install or yarn install depending on which package manager you want to use

juanma · 13 July 2020 15:57

If you’re still having problems deploying your project by following this guide
https://docs.frontity.org/deployment/deploy-using-now-vercel

Please, share a repo with the code of your project so we can try the deploy of your project and check the deployoment workflow on your project

david1 · 13 July 2020 16:42

@juanma thanks for getting back to us. It looks like @chris sorted out his issue and using that cleaning code (or a simplified version that I had used), I also sorted mine. I’m just not sure if @mhigley is still having issues…

david1 · 24 August 2020 10:12

@juanma I just wanted to say that I’ve had to use the cleaning code you posted quite regularly on two different machines. Usually it has to do with when I am developing and installing with npm inside my theme’s package. Is this something I should just always be doing or do you think this is maybe a bug?