Issues with upgrading from 0.28.25 to 0.29.1 when using yarn PnP
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- build-system
Research direction
Compare the generated declaration output from versions 0.28.25 and 0.29.1 for the curry-typed function, focusing on the missing ts-toolbelt reference and changed import path. Reproduce the Yarn PnP build with TypeScript and confirm that the declarations no longer cause the implicit-any error without requiring ts-toolbelt as a direct dependency.
Written by the indexing model from the issue text.
Description
We've recently upgraded from 0.28.25 to 0.29.1 and started having build issues along the lines of
error TS7006: Parameter 'user' implicitly has an 'any' type.
Coming from a function that looks like this (note: a lot of code has been redacted):
export const getUsers = curry(
async (id: string): Promise<User[]> => {
// ...
}
);
// ...
import { getUsers } from '@package/getUsers.js';
// the user param is the one with an implicit any
await getUsers(id)).map(async user => {
As i was looking through the differences, i've noticed that 0.28.25 produces a d.ts which includes a triple slash import
/// <reference types="ts-toolbelt" />
...
getUsers: import("Function/Curry").Curry<(id: string) => Promise<User[]>>;
whereas 0.29.1 does not do that and produces something like below
getUsers: import("ts-toolbelt/out/Function/Curry.js").Curry<(id: string) => Promise<User[]>>;
Installing ts-toolbelt in the project resolves build issues.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ramda/types
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
`intersection` should return an array of the intersection of the types of each array's elementsOpen
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day