johnlindquist / kit

Script Kit. Automate Anything.

Home Page:https://scriptkit.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

v3 Beta Roadmap

JosXa opened this issue · comments

Critical Bugs

(in order of priority)

  • (Windows) Shortcuts array for div prompt doesn't work (don't trigger handler)
  • (Windows) You cannot right-click to copy text in the chat prompt anymore
  • Highlighting text and pressing Ctrl+C to copy text out of the chat prompt always puts the entire message into the clipboard, not the selection.
  • Thank sponsors in app and on site
  • Test keyboard layout
  • Use Omit to narrow types for props that only belong on specific prompts
  • Check "quit" logic on windows
  • Make sure npm install uses ~/.knode...
  • Add "Thank you to all our sponsors" to the main menu
  • "open" scriptlets not working on windows
  • Remove old process count UI (shows up in terminal). Make terminal easier to drag
  • check npm install tsx esbuild string during startup
  • Deleting a script leaves it in the recent menu
  • Deprecate "CD" and other shelljs methods. Remove all cd in the sdk
  • Make sure remove background auto kills the script
  • ensure background auto only has one instance running
  • log results of all exec calls in the sdk
  • check grid ignore horizontal scrolling, it's not needed
  • Sequoia!!!
  • Scriptlet Shortcut metadata broken
  • tag friendlyShortcut
  • Test inspect for github issues
  • Disable scriptlets for background/automatic tasks
  • scriptlet text transform tool
  • scriptlet links, paste, files
  • Check kit run
  • Test debugger
  • fix dotenv error in terminal bins
  • Add snippets to the main menu?
  • Tray install progress text?
  • Windows - Open with from Path selector has "scandir C:\Applications" error
  • prompt x/y
  • Use the Script Kit icon
  • Show scriptlet metadata shortcut in main menu button
  • Check the requirement to right-click app to open. License issue?
  • Fix sponsor prompt. Often just displays "Type a value". Move all sponsor logic to main menu
  • Clean up sponsor splash prompt
  • Figure out sponsor prompt limit logic when trying to open the 3rd prompt
  • npm install prompt sometimes appears on wrong monitor
  • Add Scriptlets to docs
  • Point scriptkit.com/docs to https://johnlindquist.github.io/kit-docs/
  • Re-visit default scripts (one script demonstrating each prompt
  • script generator
  • Basic AI Chat
  • Check watchers and restart if failed. Touch a ~/.kit/ping.txt file and check to see if watcher picked it up
  • Replace key/mouse automation library
  • Network permissions screen on Windows when installing the app I believe this is fine. I also saw that popup for Spotify, so if a large app like that requires it...
  • open calls completely broken for URLs
  • Since 2.9.24, after any prompt (e.g. main menu) exits, the window focus is not returned to where it previously was
  • When trigging scripts via shortcut, they now always appear off-screen and cannot be moved to a visible spot. See Video. Same for the npm install popup (sometimes).
  • Resizing snaps back, see Discord. Also need to rework the height/resizing. height argument and setBounds({height: ...}) don't work at all.
  • NPM install prompts are reportedly open, but not visible anywhere on screen. See Discord.
  • Widgets completely broken: They open in the top right, show "Missing body", and behave weirdly when resizing.
  • Actions barely usable in editor & chat: See Discord (3-6)
  • lstat problem when Emojis in the filename. PR is open: #1476
  • After an await run("sub-script"), the parent script does not continue execution.
  • Snippet trigger reading, as well as snippet text pasting, are still broken on Windows
  • When the actions get updated using setActions, the overlay closes automatically. It shouldn't, as otherwise nested menus aren't possible.
  • Fix the knode archive extraction in the SDK (replace it with the app's implementation)
  • Provide various GPU configuration settings to debug NVIDIA driver performance/compatibility issues
  • debounceInput on editor debounces, but then fires the inputs for all characters in rapid succession. Generally, the debounce function works in very strange ways and the usage is unclear from just the type annotations. @JosXa to provide repro.
  • Might need to overhaul the .env writing/reading using a propery validator. Trusting/distrusting kenvs sometimes just doesn't do anything.
  • Mac 'onBlur' makeWindow/onTop not working as expected
  • Allow prompt x,y positioning
  • Check focusTab and other applescript tools
  • Quick Scripts
  • "More than 2 prompts requires a sponsorship" - don't prevent main menu or else user can seem stuck
  • Check bin generation "arg-only" is pointing to an old .js version?
  • Consider a "detachPrompt()" feature when a long-running/background script will never need it's prompt again

Minor Bugs

(in order of annoyance)

  • Likely only Windows: Whenever await run is called, on Windows the shell window pops up for a split second, causing the kit UI to lose focus. See Discord.
  • The chat prompt allows empty messages. Provide an allowEmpty: boolean and default it to false as 80% of users won't want this. Alternatively, not adding an empty message when return preventSubmit is used would also solve the issue. Re-use strict flag. Users can provide inputRegex: "\S"
  • height value in PromptConfigs is not working
  • Strange cutoff bug in chat prompt: See Discord
  • The GitHub login is very flaky. When Kit starts up, it often doesn't automatically relogin and detect your sponsor status until you explicitly click the Sign In button.
  • Hotkeys in editor (still) not overridden correctly, at least on Windows. See Discord
  • Add kenv to PATH has meaningless "Profiles" on Windows. See Discord
  • Remove the internal exists function. See Discord
  • #1428
  • await arg({..., html: md("Test")}) doesn't show a panel, but setPanel(md("Test")) onInit works.
  • Usually, you right click taskbar icons on Windows, not left. Update: Now only an issue while the status is Starting....
  • Update the node-notifier package. Its typings don't seem to match the upstream API
  • Removing scripts does not immediately have an effect in the main menu. See Discord

Potential Improvements and Features

(in order of how much JosXa wants them 😏)

  • Add actions arrays to await editor(), await term(), etc
  • Provide ability to attach an external debugger (VS Code, WebStorm, etc.)
  • Provide ability to turn NPM package installation popups off via env var
  • Add something like an onAnyScriptChanged hook. Necessary because watching ~/.kit/db/scripts.json and immediately exiting yields endless loop.
  • Reindex the available computer applications on Kit start (App Launcher)
  • Add ability to use the Windows key (meta/super)
  • widget that controls a site's JavaScript
  • Retain cursor position when setInput is called: See Discord
  • Prompt for a hotkey on first install instead of assuming QWERTY layout with ${cmd}+;. Highly requested.
  • Provide a globals.ts/.js file in the user's main kenv that automatically loads in for every script. Should provide some documentation on how to declare global in a globals.d.ts.
  • Provide a feature to force restart Kit
  • A builtin kill script (by name). E.g. https://github.com/sindresorhus/fkill
  • Allow using .env.local (and maybe .env.shared) to control which settings are gitignored and which can be checked in
  • "I should include an .env.example or something in the kenv"
  • Hide kit scripts: #1493
  • Ability to send the kit shortcut through a TeamViewer session with the remote end, not the local instance, handling the prompt