akryum / guijs Goto Github PK

Describe the bug
When opening and resizing the terminals pane, the script output doesn't resize properly, overflowing instead. Some of the output is thus hidden below without being able to scroll.

Edit: also the case with terminals.

To Reproduce
Steps to reproduce the behavior:

1. Run a script that output a lot of text.
2. Open the terminal panel
3. Resize it so it "covers" the script output
4. The output is not properly resized, preventing scrolling to the bottom.
5. The terminal is not properly resized.

Expected behavior
Output is resized and the user can scroll down to the bottom.

Screenshots

Desktop (please complete the following information):

• OS: Linux, elementary OS 5.1
• Node version: 12.16
• Are you using nvm? Yes

Additional context
Maybe overflow-hidden issues? Or Resize observer not working?

Hey !

It seems that node.js cannot be found on my mac. I think it's because I installed node with brew
The node -v command works correctly.

Desktop:

• OS: MAC 10.15.2
• Node version: 13.3.0
• Brew version: 2.2.2

i've downloaded version 0.1.19 but when selecting it in the Finder, it claims to be version 0.1.0:

neither the CFBundleShortVersionString (0.1.0) nor the CFBundleVersion (20200301.105137) have any correlation with the real version number 0.1.19

After vuejs/vue-cli#5211 is done guijs will need to handle different possible languages for the UI.

• Dynamic translation files loading
• Switch language automatically
• Language setting

Describe the bug
Script can't be run on Windows. An error is thrown about npm command not being found.

To Reproduce
Steps to reproduce the behavior:

1. Run a script

Expected behavior
The script runs.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.16
• Are you using nvm? Yes

Describe the bug
It takes a few seconds to start on Windows (~6-7 sec. on my computer)

To Reproduce
Steps to reproduce the behavior:

1. Open the app

Expected behavior
Startup time should be lower, maximum 1 or 2 seconds.

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.16
• Are you using nvm? Yes

In scripts running webpack, the progress indicator creates new line in the terminal output.

This issue should be resolved by webpack/webpack#9815

Sorry, seemed best place to log this 🤷‍♂

Just thought you should know about this (after installing debian package).

dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 25235 package 'guijs':
 missing maintainer

Describe the bug
guijs is not able to start on Ubuntu 19.10

To Reproduce
Steps to reproduce the behavior:

1. Open 'Terminal'
2. Run 'sudo guijs'
3. See error

Expected behavior
guijs is able to start on Ubuntu 19.10

Console log

***@***:/$ sudo guijs
[sudo] password for ***: 
getting @guijs/server-core version, binary guijs-server
not found
install @guijs/server-core
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
/usr/bin/guijs-server -> /usr/lib/node_modules/@guijs/server-core/dist/app.js

> [email protected] install /usr/lib/node_modules/@guijs/server-core/node_modules/node-pty-prebuilt-multiarch
> prebuild-install || node scripts/install.js

prebuild-install WARN install EACCES: permission denied, access '/root/.npm'
gyp WARN EACCES current user ("nobody") does not have permission to access the dev dir "/root/.cache/node-gyp/13.9.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/lib/node_modules/@guijs/server-core/node_modules/node-pty-prebuilt-multiarch/.node-gyp"
gyp WARN install got an error, rolling back install
gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/@guijs/server-core/node_modules/node-pty-prebuilt-multiarch/.node-gyp'
gyp ERR! System Linux 5.3.0-40-generic
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/@guijs/server-core/node_modules/node-pty-prebuilt-multiarch
gyp ERR! node -v v13.9.0
gyp ERR! node-gyp -v v5.0.7
gyp ERR! not ok 
npm WARN @nodepack/[email protected] requires a peer of @nodepack/app-context@^0.7.0 but none is installed. You must install peer dependencies yourself.
npm WARN @nodepack/[email protected] requires a peer of @nodepack/service@^0.7.0 but none is installed. You must install peer dependencies yourself.
npm WARN @nodepack/[email protected] requires a peer of @nodepack/utils@^0.7.0 but none is installed. You must install peer dependencies yourself.
npm WARN @nodepack/[email protected] requires a peer of @nodepack/app-context@^0.7.0 but none is installed. You must install peer dependencies yourself.
npm WARN @nodepack/[email protected] requires a peer of @nodepack/service@^0.7.0 but none is installed. You must install peer dependencies yourself.
npm WARN @nodepack/[email protected] requires a peer of @nodepack/app-context@^0.7.0 but none is installed. You must install peer dependencies yourself.
npm WARN @nodepack/[email protected] requires a peer of @nodepack/service@^0.7.0 but none is installed. You must install peer dependencies yourself.
npm WARN @nodepack/[email protected] requires a peer of @nodepack/utils@^0.7.0 but none is installed. You must install peer dependencies yourself.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `prebuild-install || node scripts/install.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-02-25T20_13_48_140Z-debug.log
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Error { inner: 

Cannot find binary path }', src/libcore/result.rs:1188:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
Aborted

Desktop (please complete the following information):

• OS: Ubuntu 19.10 amd 64 with all updates
• Node version: v13.9.0
• Are you using nvm? No

Additional context
guijs was installed from guijs_0.1.0_amd64.deb package

Describe the bug
Using the deb from our first release, icon is not shown in dock after launching. It also doesn't reuse the icon if it's pinned in the dock.

To Reproduce
Steps to reproduce the behavior:

1. Start guijs

Expected behavior
The icon shown in dock is correct. The icon is reused when pinned.

Screenshots

Desktop (please complete the following information):

• OS: linux, elementary OS 5.1
• Node version: 12.16
• Are you using nvm? Yes

Additional context
Seems to work on another machine with elementary OS 🤔

https://github.com/xtermjs/xterm.js/blob/49bfd05d7c71646f4fde3e44594c0d5c4d4b8536/addons/xterm-addon-web-links/src/WebLinksAddon.ts#L29

Hi guys,

I saw a link/recommendation to guijs on Twitter and thought I'd take a closer look. But, there is absolutely no documentation. What exactly does guijs do for me? How do I use it?

I downloaded the Windows install, ran it and started it. On the welcome screen there is "Import a project". What is a project? And what are the effects of doing the import? Does it affect my existing "project"? What is created?

Just being constructive here... :-)

-Tor

Downloaded the MacOS zip, tried opening it, and I'm afraid nothing happens; No application appears to open.

Tried copying to the Applications folder, still no luck.

I'm on MacOS Mojave, 10.14.6 (18G3020)

Hope it helps! Really excited to check this out :)

Describe the bug
After installation on Windows, opening the app results in a pop up stating that "VCRUNTIME140_1.dll was not found".

To Reproduce
Steps to reproduce the behavior:

1. Install the v0.1.19 Windows binary on a machine without Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 installed.
2. Open the application.
3. See error

Expected behavior
The required .dll is either included in the installation, or the README provides documentation for Windows users that the .dll (available from Microsoft here) is a prerequisite.

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.14.0
• Are you using nvm? No

Additional context
I'd be happy to submit a PR to add the documentation, if that's your preferred resolution.

Sometimes, after installing, the project generator package is not found:

ERROR  Task create-project failed Couldn't load project generator guijs-generator-nuxt

Windows installer are not available yet. They are coming soon!

Describe the bug
Terminal cursor is blinking too much or even gliching

To Reproduce
Steps to reproduce the behavior:

1. Open a terminal

Expected behavior
Cursor should blink at a normal speed.

Desktop (please complete the following information):

• OS: linux, elementary OS 5.1
• Node version: 12.16
• Are you using nvm? Yes

Additional context
Maybe it's because setBlinking is called multiple times causing multiple setInterval or similar?

After opening app , it starts downloading packages and then exits after a minute or so .

Describe the bug
On windows, different command prompts are displayed when launching the app, installing/updating the packages.

To Reproduce
Steps to reproduce the behavior:

1. Open the app or update the packages

Expected behavior
No command prompts are displayed.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.16
• Are you using nvm? Yes

Describe the bug
On Windows 10 only the Vanilla JS project generator is working for me. All the others display a loading bar on the button for a second and then revert it back to "Proceed".

To Reproduce
Steps to reproduce the behavior:

1. Install on Windows 10
2. Create a new project
3. Fill out form
4. Select generator other than Vanilla
5. Click on Proceed

Expected behavior
Displayed generators should either work or if they fail give a hint / error message.

Desktop (please complete the following information):

• OS: Windows 10 / Version 1909 / Build 18363.657
• Node version: tried with 12.16.1 and 13.9.0
• Are you using nvm? yes, nvm-windows

Is your feature request related to a problem? Please describe.
Some developers use the Windows Subsystem for Linux to build web applications on their Windows computer.

Describe the solution you'd like
Option to use the Windows Subsystem for Linux Node.js if available instead of the Windows Node.js.

.bashrc is not sourced when launching the app from the icon, as opposed to the terminal

This causes Node to either not be detected or the wrong version to be picked up (/usr/bin/node)

Suggestion for a small improvement in how the packages are shown. If the window is quite small, it only shows the version number and not the name or logo of the specific package.

I feel like the other way around would be more logical and intuitive. So showing the name (or at least the logo) and revealing more of the version number as the window gets bigger. I think it is more logical to see a list of all installed package names than a list of version numbers (without any indication to which package it belongs).

Just a suggestion for a minor improvement, maybe it helps.

This is how it is right now:

Describe the bug
On Windows, the application icon is missing in the title bar.

To Reproduce
Steps to reproduce the behavior:

1. Open the app

Expected behavior
The icon is dispplayed in the title bar.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.16
• Are you using nvm? Yes

为什么运行exe程序会自动关闭
win10环境

Is your feature request related to a problem? Please describe.
On Windows, it's a pain to have multiple Node versions, even with Windows version of nvm it means to constantly keep remembering to switch to a version since .nvmrc is not supported.

Node 10 is still active LTS till April 2021. As such it's fair to expect many people will be still using it for some time.

Describe the solution you'd like
Is GuiJS depending on some specific features of Node 12? If not, can you lower this requirement to at least v10?

Describe alternatives you've considered
Since this is GUI application, using Windows Linux Subsystem won't do any good. I am not aware of any other approach.

[Error] Failed to load resource: Error performing TLS handshake: An unexpected TLS packet was received. (apollo.png, line 0)

Describe the bug
The close terminal button is not visible

To Reproduce
Steps to reproduce the behavior:

1. Open a terminal

Expected behavior
The close button is visible and can be used to close the terminal.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.16
• Are you using nvm? Yes

Describe the bug
Closing the guijs window (thus exiting the app) may not kill the node server correctly.

To Reproduce
Steps to reproduce the behavior:
1.Close the guijs window

Expected behavior
Node server is killed

Desktop (please complete the following information):

• OS: Linux (elementary OS 5.1.2)
• Node version: 12.16
• Are you using nvm? Yes

Describe the bug
Currently you can't build most of the individual packages with the provided README instructions or npm scripts. Some seem to be missing deps.

packages/@guijs/frontend-core on  master [✘!?] is 📦 v0.1.22 via ⬢ v14.0.0 
❯ yarn build
yarn run v1.22.4
warning package.json: No license field
$ vue-cli-service build

⠦  Building for production...Browserslist: caniuse-lite is outdated. Please run the following command: `yarn upgrade`
⠧  Building for production...

 ERROR  Failed to compile with 1 errors                     3:09:58 PM

 error  in ./src/main.js

Module build failed (from /home/gnb/Sites/guijs/node_modules/thread-loader/dist/cjs.js):
Thread Loader (Worker 0)
[BABEL] /home/gnb/Sites/guijs/packages/@guijs/frontend-core/src/main.js: Cannot find module '@babel/compat-data/corejs3-shipped-proposals'
Require stack:
- /home/gnb/Sites/guijs/node_modules/@babel/preset-env/lib/polyfills/corejs3/usage-plugin.js
- /home/gnb/Sites/guijs/node_modules/@babel/preset-env/lib/index.js
- /home/gnb/Sites/guijs/node_modules/@vue/babel-preset-app/index.js
- /home/gnb/Sites/guijs/node_modules/@vue/cli-plugin-babel/preset.js
- /home/gnb/Sites/guijs/node_modules/@babel/core/lib/config/files/plugins.js
- /home/gnb/Sites/guijs/node_modules/@babel/core/lib/config/files/index.js
- /home/gnb/Sites/guijs/node_modules/@babel/core/lib/index.js
- /home/gnb/Sites/guijs/node_modules/babel-loader/lib/index.js
- /home/gnb/Sites/guijs/node_modules/loader-runner/lib/loadLoader.js
- /home/gnb/Sites/guijs/node_modules/loader-runner/lib/LoaderRunner.js
- /home/gnb/Sites/guijs/node_modules/thread-loader/dist/worker.js (While processing: "/home/gnb/Sites/guijs/node_modules/@vue/cli-plugin-babel/preset.js")
    at PoolWorker.fromErrorObj (/home/gnb/Sites/guijs/node_modules/thread-loader/dist/WorkerPool.js:262:12)
    at /home/gnb/Sites/guijs/node_modules/thread-loader/dist/WorkerPool.js:204:29
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1014:15)
    at Function.Module._load (internal/modules/cjs/loader.js:884:27)
    at Module.require (internal/modules/cjs/loader.js:1074:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/home/gnb/Sites/guijs/node_modules/@babel/preset-env/lib/polyfills/corejs3/usage-plugin.js:10:55)
    at Module._compile (internal/modules/cjs/loader.js:1185:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1205:10)
    at Module.load (internal/modules/cjs/loader.js:1034:32)
    at Function.Module._load (internal/modules/cjs/loader.js:923:14)
    at Module.require (internal/modules/cjs/loader.js:1074:19)

 @ multi ./src/main.js

 ERROR  Build failed with errors.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

To Reproduce
yarn build

Describe the bug
The window size & position is not restored.

To Reproduce
Steps to reproduce the behavior:

1. Open the app
2. Resize and/move/maximize the window
3. Close the app
4. Open the app again

Expected behavior
Window state is saved and restored:

• Size
• Maximized state
• Screen (nice to have)
• Position (not important)

xterm-addon-web-links - maybe we can do something custom with the handler

https://github.com/xtermjs/xterm.js/blob/49bfd05d7c71646f4fde3e44594c0d5c4d4b8536/addons/xterm-addon-web-links/typings/xterm-addon-web-links.d.ts#L23

here is the handler:

function handleLink(event: MouseEvent, uri: string): void {
  const newWindow = window.open();
  if (newWindow) {
    newWindow.opener = null;
    newWindow.location.href = uri;
  } else {
    console.warn('Opening link blocked as opener could not be cleared');
  }
}

https://github.com/xtermjs/xterm.js/blob/49bfd05d7c71646f4fde3e44594c0d5c4d4b8536/addons/xterm-addon-web-links/src/WebLinksAddon.ts#L29

That uses window.open()

So I think what we'll have to do is listen for that event and rewrite it to use the tauri API
The alternative would be to make a clone of the WebLinksAddon specific for tauri - although listening for the window.open() event would be easier IMHO

So this tool was loudly announced and abandoned right?

Describe the bug
Copy/paste doesn't work in xterm.

To Reproduce
Steps to reproduce the behavior:

1. Open a terminal
2. Try to copy or paste some text

Expected behavior
Ctrl+Shift+C should copy
Ctrl+Shift+V should paste

Desktop (please complete the following information):

• OS: linux, elementary OS 5.1
• Node version: 12.16
• Are you using nvm? Yes

Additional context
Maybe xterm is misconfigured.

We need to create a script to migrate the data from .vue-cli-ui to .guijs. It should be done when guijs's database structure is stable.

Describe the bug
In a Rails project, a script using bundle fails with the bundle: not found error.

To Reproduce
Steps to reproduce the behavior:

1. Have a rails project
2. Run a script containing bundle install

Expected behavior
Bundle is found & executed.

Screenshots

Desktop (please complete the following information):

• OS: linux, elementary OS 5.1
• Node version: 12.16
• Are you using nvm? Yes

Additional context
Maybe a PATH issue?

Describe the bug
App description is A Tauri app.

To Reproduce
Steps to reproduce the behavior:

1. Hover the application menu icon or go to other places where application description is displayed such as the app center.

Expected behavior
App description should be Manage your JS projects.

Screenshots

Desktop (please complete the following information):

• OS: linux, elementary OS 5.1

1. There is the @guijs/server-core which we will build and ship as a sideloaded node app in the binary space of the tauri bundle for MacOS, Linux (arch, rpm, deb, ubuntu), Windows 10 - we won't ship the node binary, expecting that the dev has it installed in their $path.

2. There is the @guijs/frontend-core which we will build and ship as the HTML/JS/CSS app in the tauri binarys space using the no-server methodology.

3. Ideally, the "first run" of the binary would do some system analysis and if the specs aren't met, then enquire if the user wants the binary to drop to an internal shell and install nodejs with nvm etc - or if it should close and let the user do that themselves.

4. Publishing an app will be made with GH Actions using the matrix like at Tauri. All node modules will be hosted at NPM - but we can build the tauri app from source.

5. Updating will be done via GH artifact download.

Todo List:

• icon creation with tauricon
• app.js and deps bundled into sideloader space (consider compression options)
• build of the frontend, transpilation for no-server drop into app-binary
• first run "wizard" and API hooks with platform and dependency detection
• CI build pipeline with "release" strategy
• updater (will require a number of utility releases to get right. probably 5-10)

Describe the bug
On Windows, scripts fail to run. There is no terminal output (the xterm instance is still created correctly), and the stop button doesn't work.

To Reproduce
Steps to reproduce the behavior:

1. Go to a script
2. Run the script

Expected behavior
The script should run, the output should be displayed and the stop button should work.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.16
• Are you using nvm? Yes

Describe the bug
On windows, the select folder dialog is opened behind the main guijs window, making it difficult to notice and use.

To Reproduce
Steps to reproduce the behavior:

1. Run the 'Import project' command
2. Click on 'Select a folder'

Expected behavior
The folder select should open in front of the other windows.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.16
• Are you using nvm? Yes

Additional context
Maybe I should port back the web based folder explorer that we can enable in the settings.

"Node.js was not found on your system"

OSX 10.15.3
node v12.6.1

Describe the bug
On Windows, the path preview uses /

To Reproduce
Steps to reproduce the behavior:

1. Run 'Create project' command
2. Select a folder
3. Enter a project name

Expected behavior
The path preview should use \ on Windows.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Node version: 12.16
• Are you using nvm? Yes

During folder selection, the pane is a windows exclusive folder structure without the ability to select network drives - which WSL is.

It would be great if we could have a full fledge folder selection pane, or if that's not possible, let us have the ability to manually enter the location.

Describe the bug

• Sometimes, the project generator selection is empty
• Path to folder project doesn't open.

To Reproduce
Steps to reproduce the behavior:

1. Go to Create a project
2. Click on Select a folder (it doesn't open)
3. Scroll down to Project generator
4. See error

Expected behavior
When project folder is clicked, the explorer files should open.
Project generator selection should always shows its list.

Screenshots

Desktop (please complete the following information):

• OS: Kubuntu 19.10
• Node version: 13.07
• Are you using nvm? Yes - version 0.35.2

Additional context

Some users can have difficulty accessing the "standard" npm registry (registry.npmjs.org), for example in China. We should have a way to configure this globally.

• server-core
• tauri-app

Since we are using npm, it's quite slow. Maybe there are ways to speed this up?

Describe the bug
When offline, the app crashes as soon as it's launched.

thread 'main' panicked at 'failed to read server package.json: reqwest::Error { kind: Request, url: "https://registry.npmjs.org/guijs-version-marker/latest", source: hyper::Error(Connect, ConnectError("dns error", Custom { kind: Other, error: "failed to lookup address information: Name or service not known" })) }', src/libcore/result.rs:1188:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

To Reproduce
Steps to reproduce the behavior:

1. Disconnect from the Internet
2. Start the app

Expected behavior
Update checks are skipped if offline or failed, the app starts normally.

Desktop (please complete the following information):

• OS: linux, elementary OS 5.1
• Node version: 12.16.0
• Are you using nvm? Yes

https://github.com/Akryum/guijs/blob/master/README.md

Then in another ...

I guess the steps before this are missing.