Forge Custom UI Confluence Macro template errors during deploy

Hi,

I created a new app from Forge custom UI confluence macro template. I didn’t modify it. Following the instructions in the README.md results in the following errors (while running forge deploy):

Error: Bundling failed: ./src/index.js
Module not found: Error: Can’t resolve ‘@forge/resolver’ in ‘/home/jfrantz/src/uitest/src’
resolve ‘@forge/resolver’ in ‘/home/jfrantz/src/uitest/src’
Parsed request is a module
using description file: /home/jfrantz/src/uitest/package.json (relative path: ./src)
Field ‘browser’ doesn’t contain a valid alias configuration
resolve as module
/home/jfrantz/src/uitest/src/node_modules doesn’t exist or is not a directory
/home/jfrantz/src/node_modules doesn’t exist or is not a directory
/home/node_modules doesn’t exist or is not a directory
/node_modules doesn’t exist or is not a directory
looking for modules in /home/jfrantz/src/uitest/node_modules
using description file: /home/jfrantz/src/uitest/package.json (relative path: ./node_modules)
Field ‘browser’ doesn’t contain a valid alias configuration
looking for modules in /home/jfrantz/node_modules
No description file found
Field ‘browser’ doesn’t contain a valid alias configuration
using description file: /home/jfrantz/src/uitest/package.json (relative path: ./node_modules/@forge/resolver)
no extension
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/src/uitest/node_modules/@forge/resolver doesn’t exist
.ts
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/src/uitest/node_modules/@forge/resolver.ts doesn’t exist
.tsx
Field ‘browser’ doesn’t contain a valid alias configuration
No description file found
no extension
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/src/uitest/node_modules/@forge/resolver.tsx doesn’t exist
.js
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/node_modules/@forge/resolver doesn’t exist
.ts
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/src/uitest/node_modules/@forge/resolver.js doesn’t exist
.jsx
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/node_modules/@forge/resolver.ts doesn’t exist
.tsx
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/src/uitest/node_modules/@forge/resolver.jsx doesn’t exist
.json
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/node_modules/@forge/resolver.tsx doesn’t exist
.js
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/src/uitest/node_modules/@forge/resolver.json doesn’t exist
/home/jfrantz/node_modules/@forge/resolver.js doesn’t exist
.jsx
Field ‘browser’ doesn’t contain a valid alias configuration
as directory
/home/jfrantz/src/uitest/node_modules/@forge/resolver doesn’t exist
/home/jfrantz/node_modules/@forge/resolver.jsx doesn’t exist
.json
Field ‘browser’ doesn’t contain a valid alias configuration
/home/jfrantz/node_modules/@forge/resolver.json doesn’t exist
as directory
/home/jfrantz/node_modules/@forge/resolver doesn’t exist
[/home/jfrantz/src/uitest/src/node_modules]
[/home/jfrantz/src/node_modules]
[/home/node_modules]
[/node_modules]
[/home/jfrantz/node_modules/package.json]
[/home/jfrantz/src/uitest/node_modules/@forge/resolver]
[/home/jfrantz/src/uitest/node_modules/@forge/resolver.ts]
[/home/jfrantz/node_modules/@forge/resolver/package.json]
[/home/jfrantz/src/uitest/node_modules/@forge/resolver.tsx]
[/home/jfrantz/node_modules/@forge/resolver]
[/home/jfrantz/src/uitest/node_modules/@forge/resolver.js]
[/home/jfrantz/node_modules/@forge/resolver.ts]
[/home/jfrantz/src/uitest/node_modules/@forge/resolver.jsx]
[/home/jfrantz/node_modules/@forge/resolver.tsx]
[/home/jfrantz/src/uitest/node_modules/@forge/resolver.json]
[/home/jfrantz/node_modules/@forge/resolver.js]
[/home/jfrantz/node_modules/@forge/resolver.jsx]
[/home/jfrantz/node_modules/@forge/resolver.json]
@ ./src/index.js 1:0-39 2:21-29

Please assist.

Hello,
I had the same problem today with my newly created Forge app. It got fixed with npm update forge.

Hope that helps,
Mateusz