This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
Only loaded in dev mode when starting atom from cmd line #1361
Description
For a while now I've been seeing some funky behavior where the github integration is only active in dev mode (e.g. atom -d) or when I've started atom by opening the Application via Finder. When running Atom this way it functions as normal but when running atom from the command line (e.g. atom) I can't use the integration at all.
It shows up as 'enabled' in Settings -> Packages and is not under the 'development packages' section, and the 'Git' panel is created but it's completely empty none of the integration commands show in command palette.
Any ideas as to what might be causing this? Can confirm this also happens in safe mode, but would be happy to post the community packages I have installed if it helps (spoiler alert: I do have git-plus).
Versions:
OS: macOS High Sierra v10.13.3
Atom : 1.26.0-beta0
Electron: 1.7.11
Chrome : 58.0.3029.110
Node : 7.9.0
apm 1.19.0
npm 3.10.10
node 6.9.5 x64
atom 1.26.0-beta0
python 2.7.10
git 2.16.2
Activity
maxwinslow-banjo commentedon May 2, 2018
Just wanted to piggyback on this issue. Same thing is happening for me. Git and Github Tab is not working when opening atom via command line
atom .unless it is in dev modeatom -d .or if I am opening it by clicking the icon in Finder.This is the error I am getting in the console.
smashwilson commentedon May 3, 2018
@tylerFowler do you have a similar stacktrace in your dev console?
@maxwinslow-banjo from the stack, this looks like an old issue (#833) that we've never been able to find a good answer for. Do you happen to have the environment variable
NODE_ENVset todevelopment? That can mess up React I'm afraid.tylerFowler commentedon May 3, 2018
Yup same stacktrace, node env is definitely development.. Interesting about the env var, I never even considered that Atom would use my env vars.
But indeed, running this:
NODE_ENV=production atom .does let it load correctly and seems to be a valid workaround for now..smashwilson commentedon May 3, 2018
Yeah, React seems to get confused when you run it with a different
NODE_ENVthan we had set while we were packaging it.Thanks for confirming. I'll close this as a duplicate of #833, then; subscribe over there for updates 🙇