-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typecheck fails for Architect create-remix-app template #6296
Comments
Is there a workaround for this? I'm having the same problem in Vercel when I try to upgrade my Remix app to 1.16.X. |
Related (duplicate?) of #4371 but for yet another template |
This adds a regression test for remix-run#6010, remix-run#6296, remix-run#6403, etc.
Also related to #6244 |
Believe it's also related to #6403 |
This is still broken in 1.17.0: "just the basics" projects created from the create-remix template still fail type checks. Is there anything that I can do to help move this along to a fix for these typecheck bugs that were introduced by #6051? #5713, #6464, and #6403 are all options that at least partially solve the problem. What would the maintainers like to do here? Would a PR to revert #6051 be considered? |
The `@remix-run/architect` package exports types that depend upon `@types/aws-lambda`, so it needs to depend (not devDepend) on it. This will fix the following error that occurs on a freshly bootstrapped Architect project generated with create-remix: ``` r$ npm run typecheck > typecheck > tsc node_modules/@remix-run/architect/dist/server.d.ts:3:135 - error TS2307: Cannot find module 'aws-lambda' or its corresponding type declarations. 3 import type { APIGatewayProxyEventHeaders, APIGatewayProxyEventV2, APIGatewayProxyHandlerV2, APIGatewayProxyStructuredResultV2 } from "aws-lambda"; ~~~~~~~~~~~~ ``` See https://stackoverflow.com/a/46011417/167694. Addresses part of remix-run#6296.
The `@remix-run/architect` package exports types that depend upon `@types/aws-lambda`, so it needs to depend (not devDepend) on it. This will fix the following error that occurs on a freshly bootstrapped Architect project generated with create-remix: ``` $ npm run typecheck > typecheck > tsc node_modules/@remix-run/architect/dist/server.d.ts:3:135 - error TS2307: Cannot find module 'aws-lambda' or its corresponding type declarations. 3 import type { APIGatewayProxyEventHeaders, APIGatewayProxyEventV2, APIGatewayProxyHandlerV2, APIGatewayProxyStructuredResultV2 } from "aws-lambda"; ~~~~~~~~~~~~ ``` See https://stackoverflow.com/a/46011417/167694. Addresses part of remix-run#6296.
Fixes this TypeScript error on newly initialized Remix projects: ``` node_modules/@types/glob/index.d.ts:29:42 - error TS2694: Namespace '"/private/tmp/my-remix-app/node_modules/minimatch/dist/cjs/index"' has no exported member 'IOptions'. 29 interface IOptions extends minimatch.IOptions { ~~~~~~~~ node_modules/@types/glob/index.d.ts:74:30 - error TS2724: '"/private/tmp/my-remix-app/node_modules/minimatch/dist/cjs/index"' has no exported member named 'IMinimatch'. Did you mean 'Minimatch'? 74 minimatch: minimatch.IMinimatch; ~~~~~~~~~~ ``` Partially addresses remix-run#6296.
This is now fixed by #6108 and will be released in v2 |
This adds a regression test for remix-run#6010, remix-run#6296, remix-run#6403, etc.
V2 release has fixed some errors but didn't fix the following two errors. Does anyone see the same issue? There's a StackOverflow discussion that addresses this issue, but I am not sure how to resolve it in my project.
|
@tommyasai That error is fixed by #7317 and is available in the latest pre-release |
@MichaelDeBoey Confirmed it works. I was using 2.0.0-pre.3. Thank you. |
What version of Remix are you using?
1.16.0
Are all your remix dependencies & dev-dependencies using the same version?
Steps to Reproduce
create-remix
.Just the basics
,(AWS Lambda)
,TypeScript
, and let it runnpm install
.my-remix-app
directory directory and runnpm run typecheck
.Expected Behavior
TypeScript type checks should complete without any errors.
Actual Behavior
The text was updated successfully, but these errors were encountered: