相关平台

微信小程序

复现仓库

https://github.com/yangxudong-functorz/taro_issues/blob/main/issue1.ts
小程序基础库: 2.17.3
使用框架: React

复现步骤

直接只用 npm run build:weapp, 报错: Module not found: Can't resolve '"},"path":"....../xxx.config.ts"

期望结果

编译成功

Hi!

On the application I currently working on, I would like to redirect my user to /#/reports/X/details instead of /#/reports/X or /#/reports/X/show when I click on one of the SimpleList line.

However, whereas the SimpleList allows to provide a custom function in linkType, and as it's name suggests, it only allow the user to return a "link type" (show or edit) as returning value.

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I am not entitled to status updates or other assurances.

Issue Type (check one)

• Bug Report

Description (type any text below) -->

When tabbing through the Spectrum interface it's difficult to know what you're interacting with since the outlines for tabbable elements have been removed.

If you force outlines back on you can see what is being tabbed.

*:focus {
    outline: 3px solid orange !important;
    outline-offse

What is the problem?

When using useQuery, the resources' type seems to get lost when destructuring setQueryData

Paste all your error logs here:

Paste all relevant code snippets here:

What are detailed steps to reproduce this?

Inspect typing with and without setQueryData

Run blitz -v and paste the output here:

$ npx blitz -v
macOS Big Sur | darwin-x64 

We should audit all our prod deps for actual usage. Discovered today that we're not using:

• marksy: https://github.com/FormidableLabs/spectacle/search?q=marksy

Opening this issue in case anyone wants to help. Recently, we've configured Storybook to import files from __examples__ folders inside Reakit component folders. This is how we're doing it:

https://github.com/reakit/reakit/blob/0b70f435673db13b75f82d69ac2760b485879674/.storybook/preview.js#L7-L22

Thos

The DatePicker component is already created and it's functional, but it was written some time ago and it can be refactored (migrating from class-based to hooks). In order to achieve a good result, we also need a good test coverage.

Running storyb