initialWorkingDirectory is not working with Hyper v3.0.0 (stable)

[berkandirim]

Updated Hyper to 3.0.0 (stable). I've noticed initialWorkingDirectory config is not picked up. Defaults to user directory.

[kiriwalawren]

I have noticed that a full reload (after opening hyper) will cause it to work.

[berkandirim]

@ecarlson94 It works but you have to do it every time you open Hyper.

[vaaski]

yes, that "fixes" it for me as well, but it's pretty annoying.

[mxmzb]

for me, a full reload doesn't make it work (currently on hyper 3.0.2).

[xtellurian]

#67

[ricardocanelas]

I am using Hyper 3.0.2

...and Full Reload woks for me:

After reload, It's opening perfectly on the initial directory as set in hyper.js

[pcnate]

Having the same issue with Powershell on Win10. The full reload seems to also fix an issue where splitting the screen doesn't always carry the cwd over.

[stnwk]

I tried to pinpoint this issue and this is what I found: https://github.com/zeit/hyper/issues/3770

Bug seems to be located in hyper codebase, so there is nothing to fix here - but I suggest we still keep the issue open until it was fixed so people can find it easier here :)

[luca-aurelia]

If you switch to the canary release channel of Hyper, this bug is fixed 🎉

Open your Hyper preferences and set the updateChannel key to canary:

module.exports = {
  config: {
    // choose either `'stable'` for receiving highly polished,
    // or `'canary'` for less polished but more frequent updates
    updateChannel: 'canary',

    hypercwd: {
      initialWorkingDirectory: '~/dev'
    }
  }
}

[xoorath]

Not working for me on Canary 3.0.2 on windows.

The full reload trick does work for me, but is obviously not ideal. :)

[james-prado]

As of version 3.1.0-canary.4 the issue seems to be resolved. The build is tagged for pre-release and can easily be installed by changing the updateChannel to "canary" in your .hyper.js config file.

It looks like this pr has been merged into the recent canary build and resolves the issue @stnwk opened.

I know the issue title specifies hyper v3.0 stable, but until v3.1 is released you'll need to use canary builds to resolve the issue.