Problem with Design View

[nshkrsh]

Wappler Version: 3.6.1
Operating System: Win10 Pro 20H2
Server Model: NodeJS
Database Type: NA
Hosting Type: DigitalOcean App Platform
Other Settings: 1 CSS file attached to the project. Using Bootstrap Local and changes made via Theme Manager.

design view on Wappler looks like this:

here as it should look like this:

nav bar blue background is on account of a class bg-blue which has been created via Wappler Theme Manager.
the logo doesn’t show either. it is placed in /public/assets/icons/ folder. on webpage it renders just fine.

[nshkrsh]

another sample:

left is the browser, right is wappler.
purple colour set as primary via theme manager. browser renders correctly but Wappler design view doesn’t!

[nshkrsh]

the problem has worsen in Wappler 3.7.4
it looks like this now:

this is the project settings:

is there anything wrong here with the config? cant seem to get the design view to work properly!
the localhost & hosted website looks and works just fine without any issues.

[George]

Well seems Wappler can’t find the files for this page.

So what kind of page is that ? Where is placed in the path? And how is the target setup?

[nshkrsh]

project is a NodeJS SPA.
design view is broken on both layout and routes.
all files made using ‘Pages’ - placed inside views folder.

there is no target - running app on localhost:3000

[NewMedia]

OK, I see you are updated to 3.7.4

[NewMedia]

Before deletion will you tell us what resolved this issue for you?

[nshkrsh]

not resolved. i was just saying that i had updated to 3.7.4 - by then you had updated your comment!

[George]

Uuuh how do you managed to have a NodeJS project without a target?

You always need at least one development target to run NodeJS locally.

So that is the root of all your problems…

[nshkrsh]

I am positive I did not remove it manually.
Will add it back and see how it goes.

[nshkrsh]

design view works after adding a target.

but even before adding target, was able to use localhost:3000 just normal! maybe disable deleting the default target for NodeJS is a good idea?