Wasp-lang•2mo ago

0.14 -> 0.15 migration + fly

I migrated from wasp 0.14 to 0.15 in my openSaaS app. After following the instructions here: https://wasp-lang.dev/docs/migration-guides/migrate-from-0-14-to-0-15 everything works great locally, but when I try to deploy on fly.io with

wasp deploy fly deploy

wasp deploy fly deploy

I get the following error, which I think might have to do with React Router 5->6: $ REACT_APP_API_URL=https://korean-language-app-server.fly.dev npm run build

[email protected] build npm run validate-env && tsc && vite build

[email protected] validate-env node -r dotenv/config ./scripts/validate-env.mjs

🔍 Validating environment variables... src/router.tsx(76,13): error TS2741: Property 'children' is missing in type '{}' but required in type '{ children: ReactNode; }'. file:///home/myusername/.local/share/wasp-lang/0.15.0/data/packages/deploy/node_modules/zx/build/core.js:146 let output = new ProcessOutput(code, signal, stdout, stderr, combined, message);

Migration from 0.14.X to 0.15.X | Wasp

What's new in 0.15.0?

5 Replies

kapa.ai•2mo ago

Hi @prof_mark. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- The error you're encountering seems to be related to the children prop in your App component. This issue was discussed in a Discord support thread (https://discord.com/channels/686873244791210014/1219134547711758416). The App component in your application is used to wrap all other components. If you've changed the App component's definition and removed the argument, it could create an error. The rest of the code is going to pass children components to App, but if the App component's definition doesn't allow for any arguments, it will throw an error. Here's how you can fix it:

const App = (_children) => {
 // ...
}

const App = (_children) => {
 // ...
}

This will define your App component to accept children. If you're still encountering issues after trying this, it might be helpful to share your code or GitHub repository with the Wasp community for further troubleshooting. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @prof_mark, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

prof_markOP•2mo ago

@kapa.ai hmm, i have a slightly different App def:

export default function App({ children }: { children: ReactNode }) {

export default function App({ children }: { children: ReactNode }) {

MEE6•2mo ago

Wohooo @prof_mark, you just became a Waspeteer level 3!

kapa.ai•2mo ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Your App component definition seems to be correct. It is defined to accept children as a prop, which is the expected behavior. The error message you're seeing suggests that somewhere in your code, you're using the App component without passing in the children prop. You might want to check your router.tsx file, specifically around line 76, as the error message suggests there might be an issue there. If you're still having trouble, it might be helpful to share more of your code or your GitHub repository for further troubleshooting. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @prof_mark, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

prof_markOP•2mo ago

i got it. I had missed a bit on the migration isntructions. I needed to change my App def to:

export default function App() {

export default function App() {

Gaming

Programming

0.14 -> 0.15 migration + fly