#error with running rts server

1 messages · Page 1 of 1 (latest)

severe spade
#

I am getting error while running yarn start for rts server. I am running it locally and it was working fine earlier. I have not made any changes to the code.

The error is -

ast/src/actionCreator/index.ts: 676:37 - error TS2339: Property 'callee' does not exist on type 'never'.

The intersection CallExpression CallExpressionMode was reduced to 'never' because property 'type' has conflicting types in some constituents.

isMemberExpressionllode (node.callee) &&

-/ast/src/actionCreator/index.ts:677:14 - error TS2339: Property 'arguments' does not exist on type 'never'. The intersection 'CallExpression & CallExpressionNode' was reduced to 'never' because property 'type' has conflicting types in some constituents.

node.arguments [argNum]

-./ast/src/actionCreator/index.ts:681:36 - error TS2339: Property 'arguments' does not exist on type 'never'. The intersection 'CallExpression & CallExpressionNode' was reduced to 'never' because property 'type' has conflicting types in some constituents.

const startPosition = node.arguments [argNum].start/

./ast/src/actionCreator/index.ts:684:14 - error TS2339: Property 'arguments' does not exist on type 'never'. The intersection 'CallExpression & CallExpressionNode' was reduced to 'never' because property 'type' has conflicting types in some constituents. node.arguments [argNum] requiredNode: I

684

../ast/src/actionCreator/index.ts:751:9 error TS2578: Unused 'ets-expect-error' directive.

// @ts-expect-error: types not matched

../ast/src/actionCreator/index.ts:753:9 error TS2578: Unused

amber smeltBOT
#

Hello! I'm Appy, your Appsmith support bot. It seems like you're encountering TypeScript errors related to type conflicts in your codebase. However, these issues are specific to TypeScript and your project's code, not directly related to Appsmith.

For the errors you're seeing, it looks like TypeScript is unable to determine the correct type for node.callee and node.arguments due to conflicting types in the union or intersection types you're using. Here are a few general suggestions to resolve these TypeScript errors:

  1. Review Type Definitions: Ensure that the types defined in your project correctly reflect the possible values. Conflicts often arise when a type is defined in multiple places or included in multiple unions/intersections with conflicting properties.

  2. Type Assertions: You might need to use type assertions to inform TypeScript about the expected type in certain contexts. For example:

    const arguments = (node as CallExpression).arguments;
    
  3. Refactor Code: If possible, refactor the code to avoid complex intersections or unions that lead to these conflicts.

  4. Update TypeScript: Sometimes, updating TypeScript to the latest version can resolve type inference issues due to improvements in the TypeScript compiler.

  5. Consult TypeScript Community: If the issue persists, consider seeking help from the TypeScript community or checking similar issues on platforms like Stack Overflow.

Since this issue isn't directly related to Appsmith, I recommend checking these general TypeScript troubleshooting steps or consulting with a TypeScript expert. If you have any questions specifically about Appsmith, feel free to ask!

If you don't find my response helpful, you can request to speak to a human agent

severe spade
#

Request to speak to human agent

amber smeltBOT
#

Someone from our team will reach out to you on this thread. In the meantime, you can have a look at our documentation to try & resolve your query https://docs.appsmith.com?utm=bot

Organizations build internal applications such as dashboards, database GUIs, admin panels, approval apps, customer support tools, etc. to help improve their business operations. Appsmith is an open-source developer tool that enables the rapid development of these applications. You can drag and drop pre-built widgets to build UI. Connect securely...

severe spade
#

Hi when can I speak to a human agent?🙂