Optimize the Image and Upload components #195
trheyiAnnotations
10 errors and 1 warning
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
|
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
|
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
|
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
|
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
|
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
|
|
Build
Element implicitly has an 'any' type because expression of type '"clear" | "key"' can't be used to index type '{}'.
|
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{ getItem: (target: object, property: string, receiver: any) => any; setItem: (target: object, property: string, value: any, receiver: any) => boolean; setExpires: (target: object, property: string, value: ExpiresType, receiver: any) => Date | undefined; removeExpires: (target: object, property: string, receiver: an...'.
|
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{ removeItem: (target: object, property: string) => boolean; getExpires: (target: object, property: string) => Date | undefined; off: (target: object, key?: string | undefined, fn?: EffectFn<...> | undefined) => void; on: (this: any, target: object, key: string, fn: EffectFn<...>) => void; once: (this: any, target: ...'.
|
|
Build
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.
|
|
Build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@v3, pnpm/action-setup@v2, actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|