Closed LySofDev closed 6 years ago
Hi, thank you for taking the time too make a good bug report. :) :100:
I saw this issue earlier, but did not realize that it was blocking. It worked my my arch. The problem is the dependencies of workflow-wm-safari
. It depends directly on workflow-wm-osx
package and triggers the error which you have correctly diagnosed. The default package.json generated by workflow
, or more specifically create-workflow-home
, depends on workflow-apps-defaults
which in turn depends on the Safari package. The direct dependency of the Safari package should have been a devDependency
, and thus not required by the npm install
you saw failing.
Remove the workflow-apps-defaults
dependency in your WORKFLOW_HOME/package.json and replace it with actual packages like workflow-app-atom
. You need too rewrite the flow files too Run npm install
manually and you should be good to go.
Change the dependencies
tag to being a devDependencies
in the workflow-app-safari
package json. And make sure that this is the only application with this issue.
Now if you want too make a PR for this I'd be delighted, but don't feel obligated too do so ;)
@LySofDev: workflow-apps-defaults@0.3.4
is released to solve this issue. Please run npm install workflow-apps-defaults@latest
in your workflow-home and let me know how if it works :+1:
Hello,
Attempting to install and use the application on Debian Linux with i3wm.
Linux Version: 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux Node Version: v8.11.1
Global installation of the package is successful yet the first run which creates the Workflow directory fails during the NPM installation process. Furthermore, attempting to use the application throws "Cannot find module ..." error for the first dependency. Inspecting the Workflow directory reveals that Node modules have not been installed.
Receiving the following error message on first use.
NPM log shows the following:
After some research, I'm under the impression that the JXA package relates to the execution of JS in a Mac OSX environment and should therefore be unrelated to a Linux environment. After inspecting the
package.json
andconfig.js
files, it would seem this dependency cannot be removed or suprressed by configuration.Please advise on how I could further contribute in the resolution of this issue.