-
Notifications
You must be signed in to change notification settings - Fork 329
VSF ui is keeps displaying error page #444
Description
Current behavior
I have not been able to get vsf ui to display properly. I consistently get the error page something went wrong.
I've tried all kinds of things and spent hours but to no avail. I keep getting the following error:
{
code: 500,
result: {
diagnosticText: "src/processor/default.ts(25,48): error TS2349: Cannot invoke an expression whose type lacks a call signature. Type 'string | ParsedQs | string[] | ParsedQs[] | ((searchString: string, position?: number) => number) | ((searchElement: string, fromIndex?: number) => number) | ((searchElement: ParsedQs, fromIndex?: number) => number)' has no compatible call signatures. ",
diagnosticCodes: [
2349
]
}
}
I've tried just using npm install, I've tried just using yarn install. I've tried running vsf ui without docker, I've tried running it with docker.
I followed all the instructions on this issue: vuestorefront/vue-storefront#4275
I've tried restricting Typescript to 3.4.1 in both vsf ui and vsf-api.
I've discarded both projects and cloned the afresh but all these attempts have yielded nothing.
What's weird is the vsf-api seems to be fine because the endpoint here returns data: http://localhost:8080/api/catalog/vue_storefront_catalog/product/_search?q=bag&size=50&from=0
The endpoint that the chrome network shows as erroring out is below:
When I try hitting this endpoint below, that's when I get the error in question about "Cannot invoke an expression whose type lacks a call signature":
I've exausted all my options as I've downloaded the vsf projects ultiple times and I keep getting the same error.
Here's my Typescript version: 3.4.1 (I also tried latest versiona and also tried 3.1.4)
@types/express version is 4.17.0
@types/express-serve-static-core: 4.16.7
Expected behavior
With both vsf-ui and vsf-api started,
When I hit localhost:3000, I should get the page with some products in it but I only get the error page telling me that something went wrong.
Steps to reproduce the issue
Setup both vsf-ui and vsf-api from current live stable repos and go visit the vsf-ui homepage
Repository
Can you handle fixing this bug by yourself?
- YES
- NO
Which Release Cycle state this refers to? Info for developer.
Pick one option.
-
This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from
developbranch and create Pull Request2. Feature / Improvementback todevelop. -
This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from
releasebranch and create Pull Request3. Stabilisation fixback torelease. -
This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from
hotfixormasterbranch and create Pull Request4. Hotfixback tohotfix.
Environment details
- Browser: Chrome, Version 81.0.4044.138 (Official Build) (64-bit)
- OS: mackOS Mojave, Version 10.14
- Node: v12.16.3
- Code Version: master