Skip to content
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

Uncaught TypeError: Cannot read property 'null' of undefined #127

Closed
HeshamAbdalla opened this issue Jun 28, 2016 · 2 comments
Closed

Uncaught TypeError: Cannot read property 'null' of undefined #127

HeshamAbdalla opened this issue Jun 28, 2016 · 2 comments

Comments

@HeshamAbdalla
Copy link

[Enter steps to reproduce below:]

  1. ...
  2. ...

Atom Version: 1.8.0
System: Mac OS X 10.11.5
Thrown From: floobits package, v0.31.3

Stack Trace

Uncaught TypeError: Cannot read property 'null' of undefined

At /Users/heshamabdalla/.atom/packages/floobits/node_modules/react-atom-fork/lib/ReactMount.js:510

TypeError: Cannot read property 'null' of undefined
    at Object.ReactMount.findReactContainerForID (/Users/heshamabdalla/.atom/packages/floobits/node_modules/react-atom-fork/lib/ReactMount.js:510:50)
    at findParent (/Users/heshamabdalla/.atom/packages/floobits/node_modules/react-atom-fork/lib/ReactEventListener.js:46:30)
    at handleTopLevelImpl (/Users/heshamabdalla/.atom/packages/floobits/node_modules/react-atom-fork/lib/ReactEventListener.js:81:16)
    at ReactDefaultBatchingStrategyTransaction.Mixin.perform (/Users/heshamabdalla/.atom/packages/floobits/node_modules/react-atom-fork/lib/Transaction.js:141:20)
    at Object.ReactDefaultBatchingStrategy.batchedUpdates (/Users/heshamabdalla/.atom/packages/floobits/node_modules/react-atom-fork/lib/ReactDefaultBatchingStrategy.js:70:19)
    at Object.batchedUpdates (/Users/heshamabdalla/.atom/packages/floobits/node_modules/react-atom-fork/lib/ReactUpdates.js:113:20)
    at ReactEventListener.dispatchEvent (/Users/heshamabdalla/.atom/packages/floobits/node_modules/react-atom-fork/lib/ReactEventListener.js:186:20)

Commands

Config

{
  "core": {
    "themes": [
      "seti-ui",
      "firewatch-syntax"
    ]
  }
}

Installed Packages

# User
firewatch-syntax, v1.0.1
floobits, v0.31.3
seti-ui, v1.3.1

# Dev
No dev packages
@ggreer
Copy link
Member

ggreer commented Jun 28, 2016

This is the same underlying issue as #121 and #123. If you launch Atom from the command line, it can erase the NODE_ENV environment variable. This can break React: atom/atom#12024

I've submitted a fix: atom/atom#12028

I'm waiting on Atom devs to approve/comment/etc.

@HeshamAbdalla
Copy link
Author

HeshamAbdalla commented Jul 6, 2016

Thank you 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants