I have a module that is “required” once during Atom load time and then again later when initialization is done and my package is running. The module’s initialization code is running both times it is required. This does not normally happen in Node. This causes me a lot of problems.
My guess is that the module cache is somehow reset or a different one is used at the end of Atom initialization. This needs to be fixed.
I will have to figure out how to make the init idempotent but it isn’t going to be easy if even possible.