alex-saunders / glicky Goto Github PK

Ain't CSS great?!? 😆

Not sure how Glicky currently handles workspaces/monorepos (any project with multiple sub-directories containing package.json files), but I know that it probably doesn't handle them well.

It would be good to get an overview of what needs fixing in monorepos and then work on fixing these bugs.

Will probably also require a UI change to support 'sub-projects'

When changing the sort order of either the scripts or dependencies list, it would be nice if the list items animated into place, rather than immediately changing position.

Maybe we could use react-flip-move?
Investigation into other libraries/solutions welcome though!

It would be good to provide functionality for empty/fresh projects (i.e. those without a package.json). In this case, the user would be alerted that this is a fresh project and guided through the process of executing npm init in order to generate a package.json file. All the options available through npm init would be available through the GUI, allowing full control. However, the options would be thoroughly explained.

Not sure the best UX for this - maybe a series of onboarding style modals (like here), though i'm up for discussion on this.

It would be nice to be able to sort scripts by prioritising those that are running so that they appear at the top of the list and falling back to alphabetical sorting on non-running scripts.

it appears on the navigator but it doesn't do anything more.

(nothing happens when you click and no vivible errors)

While #2 is being worked on, it would be good to alert the user if they open Glicky in a project without a package.json present. It would tell them that they should only open Glicky in projects that have been initialised with a package.json (via npm init).

Using this issue to add contributors

Currently, if the socket connection between the client & server dies, everything starts to silently fail and the user is given no indication of what is going on (apart from an error in the console). It would be good to alert the user via notification that the connection has failed (and maybe when they click the notification, it would attempt to reconnect to the server?).

I think using the browser's native notifications (like with the outdated dependencies notification) would suffice, there shouldn't be a need to create our own notification component/UI.

The GUI needs translations on all hardcoded strings - maybe we could use the OS' set language (or perhaps navigator.language?).

To be discussed what Intl library should be used.

Currently, glicky can't run package scripts that use commands installed in node_modules/.bin. yarn and npm do this by adding the directory to the command's subprocess environment PATH variable.

Before adding node_modules/.bin to the PATH variable

After

It would be cool to have a favicon for Glicky.
I think something along the mouse emoji theme would be cool.. maybe we could even look into getting a proper logo?

Here is a side-by-side comparison between Google chrome and the Gnome Web Browser. Unfortunately, the page crashes before anything is logged to the console.

This seems to only bother the default gnome browser but we can't be sure, maybe we should test other browsers and make a compatibility list.

Continued from #4

It would be great to use commander for the CLI commands for glicky.
Commander offers automatic generation of the --help command, which details all possible options you can pass, as well as a much more scalable architecture for adding commands/options in the future.

It would also be nice to add the --version, -v command while we're at it, which would grab the current version number from package.json and return it

I've had no means of testing on windows or linux machines and have tentatively said that Windows is an unsupported platform.

It would be good to gather examples of Glicky being tested on different platforms and the problems that are encountered, we can then work on filing issues and fixing these bugs.

Firefox:

Chrome for comparison:

This is Firefox developer edition (67.0b11 – 64-bit) running on MacOS High Sierra 10.13.4 (17E199)

I try to test this lib under my bash for Windows 10, but I've an error at start...

root@MY-PC:/mnt/d/dev/glicky# glicky
/usr/lib/node_modules/glicky/bin/index.js:39
(async () => {
       ^

SyntaxError: Unexpected token (
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:549:28)
    at Object.Module._extensions..js (module.js:586:10)
    at Module.load (module.js:494:32)
    at tryModuleLoad (module.js:453:12)
    at Function.Module._load (module.js:445:3)
    at Module.runMain (module.js:611:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:160:9)

if anyone knows what's going on....
thx