Skip to content

In JS, object is treated as 'any' #25624

New issue
New issue
Open
Open
In JS, object is treated as 'any'#25624
Labels
Awaiting More FeedbackThis means we'd like to hear from more people who would be helped by this featureDomain: JSDocRelates to JSDoc parsing and type generationDomain: JavaScriptThe issue relates to JavaScript specificallySuggestionAn idea for TypeScriptcheckJsRelates to checking JavaScript using TypeScript

Description

@ghost
ghost
opened on Jul 13, 2018

TypeScript Version: 3.0.0-dev.20180711

Code

/** @typedef {object} T */
/** @type {T} */
const x = 0;

Expected behavior:

Error at x: 0 is not an object.

Actual behavior:

No error.

Activity

  1. ghost assigned
    Nathan Shively-Sanders (sandersn)
    on Jul 13, 2018
  2. ghost added
    BugA bug in TypeScript
    on Jul 13, 2018
  3. ghost added
    Domain: JSDocRelates to JSDoc parsing and type generation
    on Jul 13, 2018
  4. ghost added
    Salsa
    on Jul 13, 2018
  5. ghost added
    checkJsRelates to checking JavaScript using TypeScript
    on Jul 13, 2018
  6. ghost removed
    Salsa
    on Jul 13, 2018
  7. ghost added
    Salsa
    on Jul 13, 2018
  8. ghost added
    javascript
    on Jul 13, 2018
  9. Mohamed Hegazy (mhegazy)
    added this to the TypeScript 3.1 milestone on Jul 13, 2018
  10. Mohamed Hegazy (mhegazy)
    removed
    javascript
    on Jul 13, 2018

  11. sandersn commented on Jul 16, 2018

    @sandersn
    Nathan Shively-Sanders (sandersn)
    on Jul 16, 2018
    Member

    I think this is a result of Object/object being treated as any. For example, /** @typedef {{}} T */ produces an error.

  12. sandersn commented on Jul 16, 2018

    @sandersn
    Nathan Shively-Sanders (sandersn)
    on Jul 16, 2018
    Member

    In getTypeFromTypeNode, we have:

    case SyntaxKind.ObjectKeyword:
    return node.flags & NodeFlags.JavaScriptFile ? anyType : nonPrimitiveType

    This was originally added in #17082. We could revisit this decision, but case-insensitive primitives and Object as any are good decisions in my opinion.

  13. Nathan Shively-Sanders (sandersn)
    changed the title [-]@typedef with no properties treated as 'any'[/-] [+]In JS, `object` is treated as 'any'[/+] on Jul 16, 2018
  14. Nathan Shively-Sanders (sandersn)
    added
    Working as IntendedThe behavior described is the intended behavior; this is not a bug
    on Jul 16, 2018
  15. Nathan Shively-Sanders (sandersn)
    closed this as completedon Aug 9, 2018

  16. 18 remaining items

  17. Nathan Shively-Sanders (sandersn)
    added this to the TypeScript 3.4.0 milestone on Jan 16, 2019
  18. Nathan Shively-Sanders (sandersn)
    modified the milestones: TypeScript 3.4.0, Backlog on Mar 13, 2019
  19. Ryan Cavanaugh (RyanCavanaugh)
    unassigned
    Nathan Shively-Sanders (sandersn)
    on Jul 26, 2019
  20. Ryan Cavanaugh (RyanCavanaugh)
    added
    Awaiting More FeedbackThis means we'd like to hear from more people who would be helped by this feature
    and removed
    In DiscussionNot yet reached consensus
    on Jul 26, 2019
  21. Ryan Cavanaugh (RyanCavanaugh)
    removed this from the Backlog milestone on Jul 26, 2019

  22. thorn0 commented on Feb 21, 2020

    @thorn0
    Georgii Dolzhykov (thorn0)
    on Feb 21, 2020

    can be closed as fixed by #35661 ?

  23. sandersn commented on Feb 21, 2020

    @sandersn
    Nathan Shively-Sanders (sandersn)
    on Feb 21, 2020
    Member

    Maybe. #35661 only applies when noImplicitAny: true though.

  24. ExE-Boss commented on Feb 21, 2020

    @ExE-Boss
    ExE Boss (ExE-Boss)
    on Feb 21, 2020
    Contributor

    I’d like if there was a way to use the object type in JSDoc without needing to enable noImplicitAny.

  25. sandersn commented on Feb 21, 2020

    @sandersn
    Nathan Shively-Sanders (sandersn)
    on Feb 21, 2020
    Member

    ExE Boss (@ExE-Boss) you can use the type NonPrimitive = object in one of your own d.ts files. Unfortunately, lots of existing JS code uses object to mean any or unknown, even projects like webpack that compile regularly with typescript.

  26. ExE-Boss commented on Feb 16, 2021

    @ExE-Boss
    ExE Boss (ExE-Boss)
    on Feb 16, 2021
    Contributor

    Nathan Shively-Sanders (@sandersn) I’ve personally been using:

    /** @typedef {(typeof Object.create) extends (arg0: infer T, ...args: any) => any
	? (T extends null | undefined ? never : T) : never} obj */

    Which is the inlined form of:

    /** @typedef {NonNullable<Parameters<typeof Object.create>[0]>} obj */

  27. DanielRosenwasser commented on May 5, 2026

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on May 5, 2026
    Member

    Keywords: object non-primitive non primitve nonprimitive jsdoc

  28. DanielRosenwasser commented on May 5, 2026

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on May 5, 2026
    Member

    Looks like TypeScript 7 might end up actually doing this.

  29. Daniel Rosenwasser (DanielRosenwasser)
    removed
    Domain: lib.d.tsThe issue relates to the different libraries shipped with TypeScript
    on May 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Awaiting More FeedbackThis means we'd like to hear from more people who would be helped by this featureDomain: JSDocRelates to JSDoc parsing and type generationDomain: JavaScriptThe issue relates to JavaScript specificallySuggestionAn idea for TypeScriptcheckJsRelates to checking JavaScript using TypeScript

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions