wardbox Comments - Answer Overflow

// =============================== IMPORTANT =================================
//
// This file is only used for Wasp IDE support. You can change it to configure
// your IDE checks, but none of these options will affect the TypeScript
// compiler. Proper TS compiler configuration in Wasp is coming soon :)
{
  "include": ["src"],
  "compilerOptions": {
    "composite": true,
    "skipLibCheck": true,
    "outDir": ".wasp/out/user",
    "module": "esnext",
    "target": "esnext",

    // We're bundling all code in the end so this is the most appropriate option,
    // it's also important for autocomplete to work properly.
    "moduleResolution": "bundler",
    // JSX support
    "jsx": "preserve",
    "strict": true,
    // Allow default imports.
    "esModuleInterop": true,
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "typeRoots": [
      // This is needed to properly support Vitest testing with jest-dom matchers.
      // Types for jest-dom are not recognized automatically and Typescript complains
      // about missing types e.g. when using `toBeInTheDocument` and other matchers.
      "node_modules/@testing-library",
      // Specifying type roots overrides the default behavior of looking at the
      // node_modules/@types folder so we had to list it explicitly.
      // Source 1: https://www.typescriptlang.org/tsconfig#typeRoots
      // Source 2: https://github.com/testing-library/jest-dom/issues/546#issuecomment-1889884843
      "node_modules/@types"
    ],
  },
}

// =============================== IMPORTANT =================================
//
// This file is only used for Wasp IDE support. You can change it to configure
// your IDE checks, but none of these options will affect the TypeScript
// compiler. Proper TS compiler configuration in Wasp is coming soon :)
{
  "include": ["src"],
  "compilerOptions": {
    "composite": true,
    "skipLibCheck": true,
    "outDir": ".wasp/out/user",
    "module": "esnext",
    "target": "esnext",

    // We're bundling all code in the end so this is the most appropriate option,
    // it's also important for autocomplete to work properly.
    "moduleResolution": "bundler",
    // JSX support
    "jsx": "preserve",
    "strict": true,
    // Allow default imports.
    "esModuleInterop": true,
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "typeRoots": [
      // This is needed to properly support Vitest testing with jest-dom matchers.
      // Types for jest-dom are not recognized automatically and Typescript complains
      // about missing types e.g. when using `toBeInTheDocument` and other matchers.
      "node_modules/@testing-library",
      // Specifying type roots overrides the default behavior of looking at the
      // node_modules/@types folder so we had to list it explicitly.
      // Source 1: https://www.typescriptlang.org/tsconfig#typeRoots
      // Source 2: https://github.com/testing-library/jest-dom/issues/546#issuecomment-1889884843
      "node_modules/@types"
    ],
  },
}

35 replies

WWasp

•Created by wardbox on 2/27/2025 in #🙋questions

Wasp typescript error

yeah it's weird lol

35 replies

WWasp

•Created by wardbox on 2/27/2025 in #🙋questions

Wasp typescript error

this is running wasp db migrate-dev after wasp clean

35 replies

WWasp

•Created by wardbox on 2/27/2025 in #🙋questions

Wasp typescript error

this one

✅ --- Database successfully set up. ----------------------------------------------


🐝 --- Building SDK... ------------------------------------------------------------


[  Wasp  ] 
[  Wasp  ]                                                                                
[  Wasp  ]                 This is not the tsc command you are looking for                
[  Wasp  ]                                                                                
[  Wasp  ] 
[  Wasp  ] To get access to the TypeScript compiler, tsc, from the command line either:
[  Wasp  ] 
[  Wasp  ] - Use npm install typescript to first add TypeScript to your project before using npx
[  Wasp  ] - Use yarn to avoid accidentally running code from un-installed packages

❌ --- [Error] Your wasp project failed to compile: -------------------------------

- SDK build failed with exit code: 1


❌ --- [Error] Compilation of wasp project failed: --------------------------------

1 errors found

✅ --- Database successfully set up. ----------------------------------------------


🐝 --- Building SDK... ------------------------------------------------------------


[  Wasp  ] 
[  Wasp  ]                                                                                
[  Wasp  ]                 This is not the tsc command you are looking for                
[  Wasp  ]                                                                                
[  Wasp  ] 
[  Wasp  ] To get access to the TypeScript compiler, tsc, from the command line either:
[  Wasp  ] 
[  Wasp  ] - Use npm install typescript to first add TypeScript to your project before using npx
[  Wasp  ] - Use yarn to avoid accidentally running code from un-installed packages

❌ --- [Error] Your wasp project failed to compile: -------------------------------

- SDK build failed with exit code: 1


❌ --- [Error] Compilation of wasp project failed: --------------------------------

1 errors found

35 replies

WWasp

•Created by wardbox on 2/27/2025 in #🙋questions

Wasp typescript error

ehhh im already going back to the normal main.wasp to try to get that working, running into the same issue though which is odd, thinking it might be package related

35 replies

WWasp

•Created by wardbox on 2/27/2025 in #🙋questions

Wasp typescript error

yea tried that, same error

35 replies

WWasp

•Created by wardbox on 2/27/2025 in #🙋questions

Wasp typescript error

could not figure this out, tried doing the npm install after clean with no luck

35 replies

WWasp

•Created by wardbox on 2/27/2025 in #🙋questions

Wasp typescript error

@kapa.ai i did run that command to install typescript i also tried going to an older version of node

  nvm use 18.18.0
Now using node v18.18.0 (npm v9.8.1)

dylank in sunderer on  wardbox/v1 [✘!] via ⬢ v18.18.0 took 2.4s 
  wasp ts-setup

[  Wasp  ] added 629 packages, and audited 632 packages in 26s
[  Wasp  ] 
[  Wasp  ] 154 packages are looking for funding
[  Wasp  ]   run `npm fund` for details
[  Wasp  ] 
[  Wasp  ] 2 moderate severity vulnerabilities
[  Wasp  ] 
[  Wasp  ] To address all issues (including breaking changes), run:
[  Wasp  ]   npm audit fix --force
[  Wasp  ] 
[  Wasp  ] Run `npm audit` for details.%                                                                                                                                                

dylank in sunderer on  wardbox/v1 [!] via ⬢ v18.18.0 took 26.4s 
  wasp start db

[  Wasp  ] 
[  Wasp  ]                                                                                
[  Wasp  ]                 This is not the tsc command you are looking for                
[  Wasp  ]                                                                                
[  Wasp  ] 
[  Wasp  ] To get access to the TypeScript compiler, tsc, from the command line either:
[  Wasp  ] 
[  Wasp  ] - Use npm install typescript to first add TypeScript to your project before using npx
[  Wasp  ] - Use yarn to avoid accidentally running code from un-installed packages

❌ --- [Error] Analyzing wasp project failed: -------------------------------------

1 errors found:
- Got TypeScript compiler errors for /Users/dylank/personal_git/sunderer/main.wasp.ts.

  nvm use 18.18.0
Now using node v18.18.0 (npm v9.8.1)

dylank in sunderer on  wardbox/v1 [✘!] via ⬢ v18.18.0 took 2.4s 
  wasp ts-setup

[  Wasp  ] added 629 packages, and audited 632 packages in 26s
[  Wasp  ] 
[  Wasp  ] 154 packages are looking for funding
[  Wasp  ]   run `npm fund` for details
[  Wasp  ] 
[  Wasp  ] 2 moderate severity vulnerabilities
[  Wasp  ] 
[  Wasp  ] To address all issues (including breaking changes), run:
[  Wasp  ]   npm audit fix --force
[  Wasp  ] 
[  Wasp  ] Run `npm audit` for details.%                                                                                                                                                

dylank in sunderer on  wardbox/v1 [!] via ⬢ v18.18.0 took 26.4s 
  wasp start db

[  Wasp  ] 
[  Wasp  ]                                                                                
[  Wasp  ]                 This is not the tsc command you are looking for                
[  Wasp  ]                                                                                
[  Wasp  ] 
[  Wasp  ] To get access to the TypeScript compiler, tsc, from the command line either:
[  Wasp  ] 
[  Wasp  ] - Use npm install typescript to first add TypeScript to your project before using npx
[  Wasp  ] - Use yarn to avoid accidentally running code from un-installed packages

❌ --- [Error] Analyzing wasp project failed: -------------------------------------

1 errors found:
- Got TypeScript compiler errors for /Users/dylank/personal_git/sunderer/main.wasp.ts.

35 replies

WWasp

•Created by wardbox on 2/27/2025 in #🙋questions

Wasp typescript error

@kapa.ai

dylank in sunderer on  wardbox/v1 [!] via ⬢ v20.18.3 
  wasp clean   

🐝 --- Deleting the .wasp/ directory... -------------------------------------------


✅ --- Nothing to delete: The .wasp/ directory does not exist. --------------------


🐝 --- Deleting the node_modules/ directory... ------------------------------------


✅ --- Deleted the node_modules/ directory. ---------------------------------------


dylank in sunderer on  wardbox/v1 [✘!] via ⬢ v20.18.3 took 5.6s 
  wasp start   

🐝 --- Starting compilation and setup phase. Hold tight... ------------------------


🐝 --- Compiling wasp project... --------------------------------------------------


[  Wasp  ] 
[  Wasp  ]                                                                                
[  Wasp  ]                 This is not the tsc command you are looking for                
[  Wasp  ]                                                                                
[  Wasp  ] 
[  Wasp  ] To get access to the TypeScript compiler, tsc, from the command line either:
[  Wasp  ] 
[  Wasp  ] - Use npm install typescript to first add TypeScript to your project before using npx
[  Wasp  ] - Use yarn to avoid accidentally running code from un-installed packages

❌ --- [Error] Your wasp project failed to compile: -------------------------------

- Got TypeScript compiler errors for /Users/dylank/personal_git/sunderer/main.wasp.ts.


❌ --- [Error] Compilation of wasp project failed: --------------------------------

1 errors found

dylank in sunderer on  wardbox/v1 [!] via ⬢ v20.18.3 
  wasp clean   

🐝 --- Deleting the .wasp/ directory... -------------------------------------------


✅ --- Nothing to delete: The .wasp/ directory does not exist. --------------------


🐝 --- Deleting the node_modules/ directory... ------------------------------------


✅ --- Deleted the node_modules/ directory. ---------------------------------------


dylank in sunderer on  wardbox/v1 [✘!] via ⬢ v20.18.3 took 5.6s 
  wasp start   

🐝 --- Starting compilation and setup phase. Hold tight... ------------------------


🐝 --- Compiling wasp project... --------------------------------------------------


[  Wasp  ] 
[  Wasp  ]                                                                                
[  Wasp  ]                 This is not the tsc command you are looking for                
[  Wasp  ]                                                                                
[  Wasp  ] 
[  Wasp  ] To get access to the TypeScript compiler, tsc, from the command line either:
[  Wasp  ] 
[  Wasp  ] - Use npm install typescript to first add TypeScript to your project before using npx
[  Wasp  ] - Use yarn to avoid accidentally running code from un-installed packages

❌ --- [Error] Your wasp project failed to compile: -------------------------------

- Got TypeScript compiler errors for /Users/dylank/personal_git/sunderer/main.wasp.ts.


❌ --- [Error] Compilation of wasp project failed: --------------------------------

1 errors found

35 replies

WWasp

•Created by wardbox on 2/2/2025 in #🙋questions

Deployed to fly.io and it auto-deployed with redis. How?

that worked ^

8 replies

WWasp

•Created by wardbox on 2/2/2025 in #🙋questions

Deployed to fly.io and it auto-deployed with redis. How?

looks like it's detected on launch but not re-deploy. im trying out 1. flyctl redis create and follow prompts, it spits out the url 2. set my env var for the redis url that it gives me 3. wasp deploy fly deploy

8 replies

WWasp

•Created by wardbox on 2/2/2025 in #🙋questions

Deployed to fly.io and it auto-deployed with redis. How?

Alrighty, trying to deploy what's on main (without redis) to a new org, then bring in redis changes and re-deploy to see how this works

8 replies

WWasp

•Created by Vladimir on 1/29/2025 in #🙋questions

is @everyone able to jump on a call and help me deploy to fly.io?

@Vladimir it may help to paste your specific errors in here and @ kapa.ai to start out. first question i'd ask is do you have it running fine locally with no errors?

21 replies

WWasp

•Created by wardbox on 1/13/2025 in #🙋questions

Wasp websockets with multi-region fly.io app

then any time after it's fine

29 replies

WWasp

•Created by wardbox on 1/13/2025 in #🙋questions

Wasp websockets with multi-region fly.io app

it seems like it's only the very first connection that is delayed

29 replies

Gaming

Programming