https://netsuiteprofessionals.com logo
Join Slack
Powered by
Has anyone been able to get the SPA apps working? ...
# sdf
c
Has anyone been able to get the SPA apps working? I am trying the simple helloworld (js version) and everything validates but when I push, i get the error below. All of my paths are correct in the object XML and i've tried two different accounts and both have the same issue. The accounts do not have any SPA apps listed. I have no idea what this error is telling me.
Screenshot 2025-08-25 at 5.31.55 PM.png,Screenshot 2025-08-25 at 5.32.09 PM.png
Screenshot 2025-08-25 at 5.34.00 PM.png
m
a
you're running 
npm run deploy
to get that error?
or are you just trying to deploy it using standard SDF? if you're using standard SDF then you're likely missing the build step which will take all the src code and create two files (which are referenced in the spa xml)
c
I don't use the CLI just the webstorm deployment which also works
In this particular case its the JS example so not transpiling occurs
so no need for a build step.. should just be here are the files and deploy
a
you need to have these files in this location, its a node process to create them
I don't think this is related to eitehr JS vs TS or webstorm vs. any other IDE
this is how SPAs work
so under src there should be a FileCabinet folder... which has its OWN suiteapps folder and then there's the suiteapps folder with your actual source code in it
when the build process runs it creates those SpaClient.js and SpaServer.js and when it deploys those are the only files it moves up to NS
I'm guessing those files don't exist and that's what's causing the error... but I don't actually know this to be the case, just my suspicion
there should also be a build folder with its own src folder, but that's just used by the build process to generate those two files, and its effectively just a snapshot of your source code at build time
it sounds like you've never done the build step so you don't actually have the files you'd need to deploy
c
Yeah I misunderstood slightly what was going on. I got the build step working and have that code in the File Cabinet path. It's still giving me the same error on deploy though. I'll keep taking a look but progress. Thank you
I got it working
🙌 1
a
good luck. glad that helped I'm new to this too so flailing around some 😄
c
The example has an assets folder that's empty. If you run npm run build or npm run deploy it'll not put that empty assets folder in the build folder
so since it was referenced in the custom object but not in the build output, it was failing
a
seems reasonable
ahh gotcha
c
Its all how you have the structures set up and it seems there's some issues w/ these examples
d
IS SPA GA now?
a
if GA means generally available? then yeah i think since 25.1?
d
Oh, cool. It used to be a thing you needed to request
a
right and even then they limited to TD accounts i think?
3 Views
Open in Slack
PreviousNext
Powered by