Wasp•3y ago

Cannot build frontend part due to type error

As you can see on the screenshot, the error is coming from

isolatedModules

isolatedModules

isolatedModules

isolatedModules flag not used in

tsconfig.json

tsconfig.json

/build/web-app

/build/web-app

/build/web-app

/build/web-app dir. This prevents building frontend.
What fixes this is either use

import type { Route } from '../../types'

import type { Route } from '../../types'

import type { Route } from '../../types'

import type { Route } from '../../types' or adding a

"isolatedModules": false

"isolatedModules": false

"isolatedModules": false

"isolatedModules": false to

/build/web-app/tsconfig.json

/build/web-app/tsconfig.json

/build/web-app/tsconfig.json

/build/web-app/tsconfig.json. But those are manual editions to the output files that is not desired. Anything that can be done on source side?

To reproduce, just generate a simple project and following Get started section, and try to build

build/web-app

build/web-app

build/web-app

build/web-app folder. I don't know if I am the only one hitting this

IamIconLivingOP•4/19/23, 8:24 AM

because folder test/vitest/test/vitest/ does not exist in generated clientclient folder, I assume it is being copied during generation process, like something like this?
https://github.com/wasp-lang/wasp/blob/a87a9ca3ec367937b39f6830bfa573e2ca14c723/waspc/src/Wasp/Generator/WebAppGenerator.hs#L60

But I can't locate the actual file where it's being copied from, so maybe there is a quick and easy thing to fix - add

type

type

to import, unless I am missing something obvious

miho•4/19/23, 8:25 AM

Could you share

wasp version

wasp version

output?

IamIconLivingOP•4/19/23, 8:26 AM

sure!

wasp version
0.10.0

If you wish to install/switch to the latest version of Wasp, do:
  curl -sSL https://get.wasp-lang.dev/installer.sh | sh -s

If you want specific x.y.z version of Wasp, do:
  curl -sSL https://get.wasp-lang.dev/installer.sh | sh -s -- -v x.y.z

Check https://github.com/wasp-lang/wasp/releases for the list of valid versions, including the latest one.

wasp version
0.10.0

If you wish to install/switch to the latest version of Wasp, do:
  curl -sSL https://get.wasp-lang.dev/installer.sh | sh -s

If you want specific x.y.z version of Wasp, do:
  curl -sSL https://get.wasp-lang.dev/installer.sh | sh -s -- -v x.y.z

Check https://github.com/wasp-lang/wasp/releases for the list of valid versions, including the latest one.

miho•4/19/23, 8:27 AM

We did a couple of minor fixes, and if you could upgrade to 0.10.2 that would probably help.

Just install it again with curl -sSL https://get.wasp-lang.dev/installer.sh | shcurl -sSL https://get.wasp-lang.dev/installer.sh | sh

miho•4/19/23, 8:28 AM

One of the fixes was adding the

type

type

next to RouteRoute reexport

IamIconLivingOP•4/19/23, 8:29 AM

gotcha! that's it, updated it and it worked!

miho•4/19/23, 8:29 AM

Let me know if it works for you

miho•4/19/23, 8:29 AM

Nice!

IamIconLivingOP•4/19/23, 8:29 AM

thank you!

miho•4/19/23, 8:30 AM

Thanks for the active feedback

IamIconLivingOP•4/19/23, 8:30 AM

in Wails, we have a built in version checker for the user, so if the user is on the outdated CLI version, we update them automatically or tell them to do it themselves
so just an idea

miho•4/19/23, 8:35 AM

That's a great idea

we were thinking about a version manager but adding automatic notice would be even better

IamIconLivingOP•4/19/23, 8:36 AM

as a side quest for myself, where are the files that you fixed the type in? I mean where are they located in project / or how are they generated, if that's not too much to cover for you? (don't want you to waste your time)
I am just looking around and getting familiar with the project's codebase, so in case things like that popup, I'd be able to contribute with a fix or whatever