Skip to content
This repository has been archived by the owner on Feb 10, 2024. It is now read-only.

Build errors #4

Open
michal-kapala opened this issue Nov 6, 2023 · 0 comments · May be fixed by #5
Open

Build errors #4

michal-kapala opened this issue Nov 6, 2023 · 0 comments · May be fixed by #5

Comments

@michal-kapala
Copy link

I've found 2 problems with the current template:

  • npm install fails - current Vite version (^2.7.2) cannot be resolved
  • wails build fails - field RGBA is missing from App structure

Vite error

Currently npm install results in:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   dev vite@"^2.7.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^3.0.0" from @sveltejs/[email protected]
npm ERR! node_modules/@sveltejs/vite-plugin-svelte
npm ERR!   dev @sveltejs/vite-plugin-svelte@"^1.0.0-next.30" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\me\AppData\Local\npm-cache\_logs\2023-11-06T13_16_27_348Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\me\AppData\Local\npm-cache\_logs\2023-11-06T13_16_27_348Z-debug-0.log

Go error

Currently wails build results in:

 • Generating bindings:   ERROR   
          # changeme
          .\main.go:34:3: unknown field RGBA in struct literal of type options.App

          exit status 1
michal-kapala added a commit to michal-kapala/wails-vite-svelte-tailwind-template that referenced this issue Nov 6, 2023
1. Bumped to Vite 3 to fix dependency resolution errors
2. Renamed the missing field in Go app template
@michal-kapala michal-kapala linked a pull request Nov 6, 2023 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant