Changelog
- Async Submenus and Dropdown: Dropdowns and ActionPanel Submenus now also support the properties
onSearchTextChange, isLoading, throttle, filtering– same as for List and Grid where you can perform custom logic when the user changes the search text. - Application: You can now get the current frontmost Application of the system with the top-level
getFrontmostApplicationmethod. - File and Directory Preferences: We’ve added two new preference types
“directory”and“file”, supported via the manifest. Both types show a file picker component and let the user select directory or file paths. - Environment: You can now get the user’s text size via
environment.textSize.
- Pop To Root Behavior:
closeMainWindowaccepts a new parameterpopToRootTypethat lets you control when Raycast pops back to root: the default is as-is and respects the user’s “Pop to Root Search” preference in Raycast.PopToRootType.Immediatecloses the window and immediately pops back to root, regardless of the user’s setting (so you can get rid of an additionalpopToRoot()call). The new modePopToRootType.Suspendedtemporarily prevents Raycast from automatically popping back to root; this is useful for situations where a command needs to interact with an external system utility and then return the user back to the launching command. - Clipboard: We added new options to copy and paste HTML content, which is useful for sharing formatted text, e.g. a link to a Notion page in Slack.
- Markdown: Markdown in a
Detailcomponent now supports convenience image references for icons and asset folder files such as:or(absolute URLs and user folder paths via~are also supported) - OAuth: The client’s
providerIconis now optional (extension icon as default) and accepts anImage.ImageLiketype. - List and Detail Metadata: Now show tooltips when labels get truncated.
- Action.ToggleQuickLook: Now also expands paths starting with
~.
- Dropdown: Fixed triggering a dropdown component’s
onChangehandler when navigating. - Dropdown: Fixed the missing
placeholderproperty in the search bar dropdown. - Forms: Fixed submitting a form with marked text.
- Actions: You can now specify an action to focus when opening the ActionPanel (and an ActionPanel.Submenu) by setting the
autoFocusprop. - Forms: Introducing a new Form Item
Form.FilePickerto select one or multiple files (or directories)
- DX: A warning will now be shown in the console when using async entry points for view and menu-bar commands.
- List/Grid: Improved the keyword search algorithm to match intersecting keywords (for example, the search term ”black cat” matches keywords [”black”, “cat”]).
- Grid: The grid supports a new property for configuring how sections are ordered. Setting
filtering={{ keepSectionOrder: true }}ensures that the sections' order is not changed based on items' ranking values; this can be useful for use cases where a small number of fixed sections should always appear in the same order when the user filters the grid. We are deprecating theenableFilteringproperty.
- Fixed the Grid or List’s selection sometimes not being preserved when native filtering is disabled.
- The
Image.Mask.RoundedRectanglemask will be more consistent regardless of the size of the image. - Fixed an issue where the specified
searchTextproperty would not always be respected.
- Commands can now launch other commands! Using the new
launchCommandmethod, you can now trigger a background refresh of another command in the same extension - or even open another command. Some use cases are updating a menu bar command from a view command or, vice versa, launching a companion view command from the menu bar. (Note that for now we only support launches of other commands within the same extension.)
- Grid now supports two new aspect ratios: 4/3 and 3/4.
- Menu Bar icon tinting is now theme-aware.
- Background Refresh: The shortest interval available is now 10s instead of 1m (use cautiously and also see our best practices guide).
- Grid: The grid supports a new property for configuring how sections are ordered. Setting
filtering={{ keepSectionOrder: true }}ensures that the section order is not changed based on items’ ranking values; this can be useful for use cases where a small number of fix sections should always appear in the same order when the user filters the list. We are deprecating theenableFilteringproperty.
- List Item Metadata Link and Detail Metadata Link styling should now be consistent with their respective List Item Metadata Label and Detail Metadata Label respectively.
- Fixed a bug where
List.Item’s accessories might not be aligned. - Fixed a bug where the last API call or log in a no-view command would not run before the command gets unloaded.
- Grid: the
Gridcomponent accepts three new props that should give extension authors more flexibility:columns,fitandaspectRatio.
- Grid Sections don’t all have to look the same anymore! The grid
Sectioncomponent now also accepts thecolumns,fitandaspectRatioprops. When specified, they will override the value of the parentGridcomponent’s prop. - List: The list supports a new property for configuring how sections are ordered. Setting
filtering={{ keepSectionOrder: true }}ensures that the section order is not changed based on items’ ranking values; this can be useful for use cases where a small number of fix sections should always appear in the same order when the user filters the list. We are deprecating theenableFilteringproperty. - Menu Bar Extra: added a new
Sectioncomponent, which can be used to better group relatedItems and/orSubmenus. The component has an optional title for the section. At the same time, we are deprecating theSeparatorcomponent. - Menu Bar Extra: The
Itemcomponent now accepts an optionalsubtitleprop. - Clipboard:
Clipboard.copy()andClipboard.paste()methods now accept file paths as a parameter.
- Improved dark/light mode detection for Menu Bar Extra icons.
- If a Menu Bar Extra’s
titlespans multiple lines**,** only the first one will be displayed.
- Fixed certain error stack traces causing CPU spikes of the Node process.
- Fixed an issue with macOS Ventura Beta where Menu Bar Extras would sometimes become unresponsive.
- Fixed the type of the List and Grid’s
onSelectionChange. It always used to returnnullwhen no items were selected but the type wasstring | undefined. It is now properlystring | null. Note that this might trigger some TypeScript error when you upgrade but it should help you fix some bugs.
- Menu Bar Extras can now be deactivated without disabling the menu bar command! To deactivate a menu bar command, run the
Deactivate Commandaction from the command's Action Panel - or drag the menu bar extra out of the menu bar while holding down ⌘. - Commands with Background Refresh also now have a
Deactivate Commandaction! - Menu Bar Extras now support both a primary and secondary action type (right click or control click).
- Dropdown's items can now specify
keywordsto match more search terms. - Extension Diagnostics command can now be used to help finding the cause behind any issues with extensions. It displays all
Loaded Commands, commands withBackground Refreshenabled and latestEventstriggered.
- Menu Bar Extra action handlers will now either wait or force a render after finishing execution, to ensure any state updates performed in the action handler have had a chance to render.
- Menu Bar commands now automatically refresh when their or their parent extension's preferences change.
- OAuth: Path-based redirect URLs are now officially supported.
- OAuth: ⚠️️ API methods for OAuth request creation now throw an error when used from a background command - you can check the launch type of a command to see whether authorization can be performed
- Types: Node and React types have been added back as optional API peer dependencies and dev dependencies to the templates, so that VS Code autocompletion works.
- Templates: Updated to include the utils package.
- DevX: Added warnings when specifying a
valuewithoutonChangeor when changing a Form item from controlled to uncontrolled. - DevX: For starting development, the CLI does not depend on metadata attributes any more
- Forms: The type of the
DatePicker's value is nowDate | null(nullhappens when selectingNo Date). ⚠️ This might cause some TypeScript errors but it will now reflect what is really happening, preventing bugs at runtime. - Fixed an issue where
List.Item.Detail.Metadatatitles sometimes being cropped despite there being enough room. - Menu Bar Extra
ItemandSubmenuicons now change based on the system's dark / light mode, not Raycast's. - Forms: Fixed a bug where the initial value for a controlled TextArea could not be deleted.
- Forms: Fixed the info icon and message not coming back after clearing an error on form items.
- Forms: Fixed updating the placeholder of the TagPicker item.
- Empty View: Fix an issue where an Empty View's actions would be rendered even thought the Empty View isn't.
- OAuth: Fixed a bug where multiple overlays could stack upon each other when OAuth was initiated from a menu bar or background launched command
- Bundler: You can now import wasm files and they will bundle in the extension
- SVG: Accept a percentage for rect corner radius attributes
- Actions:
Action.Trashis now a Destructive Action (meaning it will show up in red)
- Metadata: Fixes an issue where List Metadata would sometimes render Tags in the wrong position
- List.Item.Detail.Metadata: We've added support for new
LinkandTagListitem types. - Environment: You can now check the
modeof the current command (as defined in the manifest) viaenvironment.commandMode.
- CLI: The ray CLI is now code-signed
- CLI: We've updated esbuild to v0.14.52
- NPM size: is now 0.5MB instead of 25MB (binary files for ray CLI have been moved out of the NPM package)
- Navigation: Top-level components can now dynamically return a different view type when used inside a navigation stack
- Background Refresh: Fixed an edge case where commands would run into a timeout that prevented further refreshing
- Menu Bar Commands: Fixed a bug where the error screen of menu bar commands would repeatedly be shown in the root search
- Actions: Triggering actions by numeric shortcut / double-clicking could trigger wrong actions or didn't work entirely
- Form:
TextAreaplaceholder now won't highlight markdowns if it hasenabledMarkdown
- Added debug actions to all local development commands in root search
- Menu bar commands now show an activation button in preferences
- Menu Bar Commands: Fixed issues around hot reloading, unloading, and inconsistent action handler behavior
- No-view Commands: Fixed returning top-level props for commands that doesn't have arguments or drafts
- 🍫 Menu Bar Commands (Beta): For a long time, Commands could only live in the Raycast window. From today, Commands can put glanceable information in the Menu Bar 💪. Check out our new docs section on how to develop your first native macOS menu bar command with hot reloading 🔥.
- 🔄 Background Refresh (Beta): To keep Menu Bar Commands up-to-date, we ported Background Refresh from Script Commands to Extensions. Background Refresh is configured with a new interval option in the Extension's manifest and also works for "no-view" mode commands. Read more about it in a new docs guide.
- 🪝 Utils: We've released new React hooks to make it faster to build extensions that follow best practices. To do this, we looked at the Extension's repository for use cases and how we can improve them. Most Extensions connect to APIs: they make network requests, show a toast to handle errors, and add caching and optimistic updates to speed up interactions. Utils are available via a new public npm package.
- 🤬 Arguments: We also ported more functionality from Script Commands. Extensions can now define arguments, which enable simple forms that live in the root search of Raycast. Arguments can be defined via the manifest, and their entered values are passed to the main function of a command.
- ✍️ Subtitle Updates: We've added a new method
updateCommandMetadatathat allows you to update the subtitle of a command in root search. Combined with Background Refresh, this is another way to present information to the user as dashboard-like items in the root search.
- Redesign: Along side the app's redesign, we are introducing a whole set of new icons for you to pick to illustrate the actions in your extensions.
- New Destructive Action: You can now specify the
styleof anActionto highlight it in the Action Panel as destructive. Use it for actions where an end-user should be cautious with proceeding.
- DevTools: Turning on the "Use Node production environment" in the Advanced Preferences will also hide the debug actions. Previously it was only hiding them when there was no Action Panel specified.
- DevTools: The "Clear Local Storage" debug action has been renamed to "Clear Local Storage & Cache" and will clear the Cache along side the Local Storage.
- Dev Tools: The "Start Development" action now quotes the extension folder path.
- Dev Tools: Added a new development advanced preference to keep the Raycast window always visible during development.
- Dev Tools: Added a new build status tooltip to the accessory icon of a development command in root search.
- Dev Tools: Improved the error handling for failed extension updates after invalid manifest changes; improved the error messages for general rendering errors.
require('os').tmpdir()will now properly return the path to a temp directory.- Fixed a rarely occurring crash happening when using some SVGs with a path that contains an arc where the ending point is the same as the starting point.
- Forms: Fixed a bug where stored form values could get cleared after extension updates.
- Forms: Fixed inconsistent behaviour of the
onBlurhandler that could get triggered for theForm.TextFieldwhen the form screen is popped in a navigation stack. - List: Fixed the updating of tooltips for list accessory items.
- React 18: React Suspense,
useSyncExternalStore, etc.. A whole bunch of new features are available with the newest version of React. See the migration guide for more information. - Quick Look: Use the new
<Action.ToggleQuickLook />action to show additional information with a Quick Look preview. - Forms: Use the new validation feature to check if entered data is correctly formatted and show failure messages with a nice UX
- Forms: Drafts support - use the feature if you want Raycast to preserve non-submitted data, to provide the best experience for users
- DevX: Check out the new screenshot tool that takes a photo of Raycast from the best possible angle
- List Accessories: You can now pass
{date: Date}as an accessory and it will be rendered nicely by Raycast. - Detail View: Add support for
- [ ] taskand- [x] taskin markdown views. - Action Panel: Add a new
onOpencallback onActionPanel.Submenu. It can, for example, be used to lazily fetch the content of the Submenu. - Grid: Add support for
ColorLikeas Grid.Item's content. - Forms: New callbacks
onFocusandonBlurfor all the items - Forms: Markdown highlighting for the
Form.TextArea
- Misc: Fixed a crash when using
<List>{response?.website && <List.Item title={response.website} />}</List>andwebsiteis an empty string (Issue 1845). - Dev Tools: Fixed uninstalling of local development extensions via the Action Panel
- Markdown: Fixed rendering of transparent animated gifs in markdown
- List Accessories: Fixed the tooltip for grouped accessories; now the tooltip will be shown for the group instead of separately for the items
The
<Grid /> component's made its way to our API. It's perfect to layout media-heavy information, such as icons, images or colors. The component allows you to layout differently sized items. We designed its API close to the <List /> component for smooth adoption.- Fixed the controlled mode for
Form.DatePicker - Fixed the dynamic appearance of form item's
infoaccessory - Fixed the OAuth logout preference not being shown for single-command extensions
- Fixed a bug where components that are pushed with the same properties values would not be updated (Issue 1843)
- Fixed a bug where updated list metadata items would cause unnecessary list reloading
- Fixed an issue with tinted, resized icons appearing blurred in some cases (e.g. Alerts)
- List Item Metadata: we've added a new
metadataproperty to theList.Item.Detailcomponent, allowing you to add structured metadata. Themetadataproperty can be used together withmarkdown, in which case the detail view will be split horizontally, with the markdown being displayed in the top half and the metadata displayed in the bottom half (similar to theFile Search,Clipboard HistoryorSearch Contactscommands). Alternatively, it can be used by itself, in which case the metadata will take up the entire height of the detail view. - Preferences: We've added two new top-level methods
openExtensionPreferencesandopenCommandPreferencesthat allow you to open both extension and command preferences, for example, via an Action (Issue 179)
- Added a new development action to clear the local storage of an extension
- Fixed a bug where the wrong form element onChange handler would be called initially while the form was being updated (Issue 1633)
- Fixed
EmptyViewnot being displayed when it would be reused in a navigation stack
- OAuth: TokenSets are now included in the encrypted Raycast export (Raycast Preferences > Advanced > Export)
- OAuth: The convenience method
TokenSet.isExpired()now includes some buffer time to reduce the risk of performing requests with expired access tokens
- Fixed an issue where updating the search bar accessory would result in the search bar text being selected
- Forms: We've fixed some inconsistencies around form item properties and added new warnings (e.g. when
defaultValueandvalueare set at the same time); this also fixes Issue 1104 - Forms: Fixed an issue where updating form items would lead to unwanted scrolling; fixed the
autoFocusproperty not scrolling to the focused item - Fixed an issue with
Action.OpenWithtrying to perform a state update without checking whether it's still mounted (Issue 1495). - Fixed an issue where
adjustContrastwould not be respected for colored TagPicker items.
- OAuth: we've added a new API that enables you to authorize extensions through OAuth providers such as Google, Twitter, Dropbox or Spotify (Issue #178). The docs contain a new detailed guide and we've added some integration examples to the extensions repository. (Note that we currently only support OAuth 2.0 with PKCE, more on that in the guide.)
- Form Focus: use the new imperative form API to programmatically focus form items. Want to make sure a particular input is focused on mount? Form items now accept an
autoFocusprop! (Issue #66) - Form Reset: use the new imperative form API to reset form items' values to their initial values.
- Form Info: Use the new
infoprop on form items to show additional information about an item, e.g. to explain what this field is used for. - The Raycast window opens automatically when you start a development session for an extension. You can turn the behavior off in the Advanced preferences tab.
- Improved detection of default editor when you open extensions from Raycast
- Improved templates for list, form and detail
- Removed
react-devtoolsfromdevDependenciesfor newly created extensions (so that you don't have to download a big dependency that you might not use)
- Fixed an issue where animated gifs would be incorrectly scaled when size attributes are specified in markdown.
- Form Checkbox now returns proper boolean values on submit
- List Tooltips: List items now support tooltips for the title, subtitle, icon, and each accessory item. For titles, you can use the new type
{ value: string, tooltip: string }, for icons{ value: Image.ImageLike, tooltip: string }, and for accessories you just add the new propertytooltip. - Animated Gifs: the
Detailcomponent now renders animated gifs defined in markdown! 🎭
- Improved recovering the Node process after a crash and logging the error to the CLI output
- Added support for running CLI commands through
npx @raycast/api <commandName> - Improved the
Create Extensioncommand to addREADME.mdandCHANGELOG.mdfiles
- Detail Metadata: Fixed toggling (showing/hiding)
- Detail Metadata: Fixed only one separator item getting rendered
- Detail Metadata: Fixed a crash when using primary or secondary colors for tag items
- List Accessories: Fixed rendering when using
undefinedfor accessory values - List EmptyView: Fixed an issue where passing a
List.EmptyViewchild to aList.Sectionwould treat it as aList.Item - SVG: Fixed rendering base64 encoded SVG images
- Fixed loading when a new command is launched by hotkey while another command is open
- Detail Metadata: we've added a new property
metadatato theDetailcomponent; this allows you to add structured metadata that is displayed on the right side in a detail view (similar to the Linear, Asana or Jira extensions). We support types such as labels, coloured tags, links, and separators. (Issue #219) - List Accessories: list components can now show multiple accessory items through the new
accessoriesproperty. (Previously you could only configure oneaccessoryTitleandaccesoryIcon, both of which continue to work but have been marked deprecated.) Each item can be configured as text-only, icon-only, or icon + text. (Issue #72) - List Empty View: list components can define a new
EmptyViewthat gives you control over the icon, title, description and optional actions to use when there are no items in a list. (Previously we would default to a "No results" view.) You can use the component to show a custom image and text when the search does not return results or the user is required to first perform some setup. (Issue #447)
- Environment: the current theme (
"dark" | "light") configured via Raycast appearance preferences is now globally accessible throughenvironment.theme - SVG: You can now specify width and height attributes for images in markdown (
<img>tag). - Dev Tools: the "Create Extension" command lets you add categories to your extension; the categories are displayed alongside the new metadata on our revamped details page in the store.
- Dev Tools: added a new development action to clear the local assets cache, e.g. to render an updated list icon without having to restart Raycast. (Issue #1095)
- Preferences: the
requiredproperty in manifest preferences is now optional.
- Fixed the extension icon not being updated during development.
- Fixed an extension's cached icon not being cleared when updated from the store. (Note that other dynamically loaded images in the assets folder may still be cached, so if you want to enforce an update for end users you need to rename them.)
- Fixed an edge case where some search bar characters would be wrongly passed to pushed lists in a navigation stack.
- Fixed updating the list
isShowingDetailproperty - Fixed unnecessarily reloading the list detail view on search term changes
- We've added the highly requested search bar dropdown 🎉 (Issue #72): you can now add a dropdown component as an accessory to the search bar; the dropdown shows up in the top-right corner and can be used for filtering lists and toggling list states. (So it's a good time to remove any workarounds with actions or navigation for showing a different set of items in the list.)
- The search bar text 🔎 can now be programmatically updated (Issue #281) while you can still opt into built-in filtering at the same time
- List-detail views: list views now support a
detailproperty that allows you to display a detail view on the right-hand side of list items (Issue #83) 👯♂️; you can use the feature to display additional content side-by-side as users scroll through the list - Support for rendering SVG files 🖼️ where images are accepted (Issue #77), including in the
Detailview's markdown - New method
Clipboard.readText()to read the last copied text from the system's clipboard 📋 - Added a new prop
typetoForm.DatePicker📅 to control the date components asked from the user
- Toast action handlers 🍞 can now still be called if the toast outlives a dismissed extension
- Support for multiple actions of type
Action.SubmitFormin a form's Action Panel
- Fixed some flickering that could happen when using
React.memo - Fixed a few edge cases around Action Panels
- Fixed duplicated shortcut shown in the Action Panel's tooltip when setting the default shortcut explicitly on the primary action
- Fixed updating a
Form.Descriptioncomponent
- Add 2 new Actions:
Action.CreateSnippetandAction.CreateQuicklink. Use them in your extensions to provide users an option to integrate deeper with Raycast, for example, by creating a Quicklink from a frequently visited website.
- Various documentation fixes and improvements such as new media for UI components.
- Synchronous React state update calls are now batched, leading to less re-rendering.
- Markdown comments will now be hidden in the
Detailview
- Fixed a crash that could happen when switching between a development and store version of an extension or restarting the Node connection.
- Fixed an issue with React Developer Tools sometimes not getting opened.
- Limit the width that the
ActionPanelcan take.
- Completely revised (backwards-compatible) API - new namespaces, better organisation, more consistency, updated templates, revamped docs. Check out the full migration guide and get rid of those deprecation warnings. (At the same time, don't worry, your extension is going to work as before, even if you don't take immediate action.)
- We've prettified the CLI output 💅: all output is now more colourful, cleaner and easier to parse. Update the npm package to v1.28.0 to get the latest CLI for development.
- Fallback images: You can now specify local asset files or built-in icons that are displayed when image loading fails, for example when a remote file is missing (Issue #108); see the docs
- Toasts are now passed as argument to their action callback, so you can directly act on them in the handler function (for example, hiding them)
- Extensions feedback: We've added better bug report and feature request actions both to the store details page of an extension and to the error screen; the actions prefill some data already in the templates so that reporting issues and feature requests becomes easier for end users.
- Preferences: Added a new app picker preference type - useful if you want to let users customize their apps to use for opening files, folders and URLs Issue #98
- Forms: Added new
Form.PasswordFieldthat allows you to show secure text fields (Issue #319 and Issue #44) - Forms: Added new
Form.Descriptioncomponent that allows you to show a simple label - Added a new top-level
openmethod that gives you more flexibility for opening files, folders, and URLs with default apps or specified apps, often making using an external npm package unnecessary (the built-in open action use our method under the hood) - Node: added security enhancements for the managed Node runtime such as verification of the executable, configuring executable permissions, and removing unnecessary files
- CLI: Added more error info output to build errors
- CLI: Added a new
—fixflag to thelintcommand (applies ESLint and prettier fixes) - Create Extension Command: Updated the templates to include a
fix-lintscript; added prettier to devDependencies
- Forms: Fixed
onChangecallback behaviour to be consistent across all components - Preferences: Fixed a bug in dropdown preferences returning the defined default value, even if the default is not part of the list values
- Preferences: Fixed the
dataproperty not being treated as required for the dropdown - Preferences: Fixed defined initial values not being ignored (use default only)
- List: Fixed same-rank items with identical names being non-deterministically ordered
- Fixed a bug with open actions causing double opening via the default and specified app
- CLI: Removed auto-installation of npm dependencies through the downloaded npm
- Developer Tools: Added
Open Support Directoryaction to local dev extensions - Developer Tools: Removed auto-injecting of globals for enabling React Developer Tools in dev mode
- Developer Tools: Added
prettierchecks to CLIlintcommand - Documentation: Updates and fixes
- Forms: Fixed controlled updates for the
Form.TagPicker - Navigation: Fixed a bug where a programmatic pop, followed by a manual pop (e.g. ESC) could lead to wrong state (Issue #571)
- New API for Alert views: Alerts are useful for destructive actions or actions that require user confirmation; new methods let you display our beautiful native Alert component (Issue #48)
- New API for interactive Toasts: you can now add buttons to Toasts, e.g. to give the user options for created items, to open the browser, or for any other relevant context (Issue #438)
- New API for retrieving the current Finder selection: unlocks a couple of use cases for extensions that perform actions on selected files and folders (Issue #153)
- Improved ranking for fuzzy search in lists with sections and keywords
- The icon of the
OpenWithActioncan now be customised - The env var NODE_EXTRA_CA_CERTS is now being propagated so that custom certificates can be configured
- Textfields do not auto-transform certain characters such as dashes any more (Issue #491 and Issue #360)
- This CLI of this version contains an update of the build tool with changed (and "more compatible") heuristics around how
defaultexports are handled. This means that you should double check whetherimportstatements for certain npm packages need to be adjusted. Example:import caniuse from "caniuse-api"has to be changed toimport * as caniuse from "caniuse-api"because of the missingdefaultexport of the builtcaniuselibrary that has to run in a Node environment.
- Keywords added to list items are now matched again by prefixes (exact matches were required previously)
- Extensions are now checked for version compatibility before updating and installation
- New and updated templates available in the "Create Extension" scaffolding command
- Modifications to list item keywords could result in wrong list filtering
- Fixed a regression where the CLI would not automatically install dependencies when building the extension
- DatePicker form element now returns the time component when specified
- Animated toasts are now automatically dismissed when the extension is unloaded
- Forms don't accidentally trigger draft creation mode any more
- Extensions which are off by default are now correctly disabled
- Full fuzzy search by default for lists using built-in filtering
- Faster list loading times
- Better default auto-layout of list item title, subtitle and accessories
- Extension support directory does not need to be explicitly created any more
- Raycast is no longer automatically brought to the foreground for failure toasts
- New default action to open a bug report on production error screens in extensions
- Updated extension icons are now displayed without having to re-install the dev extension
- Focus is now kept on the current form element when re-rendering
- Caret does not jump to the end of the string in controlled textfields and textareas any more (one edge left that is going to be tackled in one of the next releases)
- "Disable pop to root search" developer preference is now only applied for commands that are under active development
- Documentation fixes and updates
- Updating of items and submenus while the action panel is open
- Supporting all convenience actions with primary shortcut (cmd + enter) on form views
- Better error handling when the API cannot be loaded after failed app updates
- Loading indicator in detail views when used in a navigation stack
- Improved ActionPanel updating performance
searchBarPlaceholderupdates when using the list in a navigation stack- Wrong action panel actions when popping back in a navigation stack
- Empty state flickering when updating the
isLoadingproperty in lists - Accessory and subtitle label truncation in lists
- Icon from assets tinting on dynamic theme changes
- Dynamic removal of form elements
- Open actions leading to Node env vars being set for the opened application
- Some extensions not getting loaded for a particular Node setup
- Local storage values being lost when extensions are automatically updated
- Fixed configuring
tintColorfor icons inActionPanelandForm.Dropdown - Fixed displaying submenu icons from local assets
- Fixed tinting of icons provided from local assets
- Fixed a crash with the
getSelectedTextfunction - Fixed the main window sometimes not shown when an error is thrown from a command
- Fixed the
OpenWithActionnot working for some apps - Fixed the list empty state not being shown in certain cases when using custom filtering
- Fixed the the topmost item not automatically being selected for custom list filtering
- Fixed the line number info in error stack traces sometimes not being correct
- Fixed an issue where installing store extension would sometimes fail
- Fixed a crash that could be caused by sending invalid codepoints from an extension
- Fixed a bug where no error would be shown when the runtime download failed
- Fixed reaching the max. call stack size when logging recursive object structures (this could happen when you console logged a React component, for example).
It's happening! We're opening up our API and store for public beta.
This is a big milestone for our community. We couldn't have pulled it off without our alpha testers. A massive shoutout to everybody who helped us shape the API. Now let's start building. We can't wait to see what you will come up with.
Last modified 14d ago