Describe the bug
Creating angular project with no initial app throws sb init error
• Detecting project type. ✓
• Adding Storybook support to your "Angular" app
TypeError: Cannot read property 'architect' of undefined

To Reproduce
Steps to reproduce the behavior:

1. ng new ng-ui --create-application=false
2. cd ng-ui
3. ng g lib button -p ui
4. npx -p @storybook/cli sb

问题描述
最近使用movable-view做了一个拖拽排序的功能，但是由于需要touchmove事件频繁setState来更新movable-view的坐标，导致Android的上的性能体验很差，IOS不会。

看了微信的文档，这种情况可以使用WXS来解决，请问Taro中能否使用WXS？如何使用呢？

参考文档: https://developers.weixin.qq.com/miniprogram/dev/framework/view/interactive-animation.html
https://developers.weixin.qq.com/miniprogram/dev/framework/performance/tips.html

🚀 Feature request

Current Behavior

The type ErrorMessage doesn't have an id property.

Desired Behavior

It'd be nice id?: string would be added to the type ErrorMessage and set on the outermost component that serves as error message.

Suggested Solution

Add id={this.props.id} to the outer component in ErrorMessage.

Who does this impact? Who is this

Summary

When using a slash command that crashes a plugin, the user receives an unfriendly message.

Observed:

Command with a trigger of '/jira' not found. Click here to send as a message.

Expected:

Plugin for the jira command is not working. Please contact your system administrator.

Ticket Link

https://mattermost.atlassian.net/browse/MM-24753

Related: react-navigation/react-navigation#8160

We have a similar guide for React Router + Netlify https://github.com/expo/examples/tree/master/with-react-router#deploying-to-netlify

We should also have one for Now:

• Create now.json:

{
  "version": 2,
  "routes": [{ "handle": "filesystem" }, { "src": "/.*", "dest": "/index.html" }]
}

Currently, the Ctrl+Shift+B shortcut is assigned to focus the note editor. However, when the current layout is viewer-only, it doesn't make sense to focus the editor. Instead it should focus the viewer panel.

A bit of context, we introduced swr two weeks ago to our codebase. Everything is working fine, but we started to get some reports about some parts of the app being broken in slightly older browsers (Chrome 49, Firefox 59, Edge 18, etc…)

We found out that swr was causing a syntax error in these browsers because webpack by default picked the ESM build (rightly so) but because it's not transp

Doesn't seem to happen for previews of sites.

...this boilerplate is awesome, thank you for sharing it guys 👍

Move all Travis' scripts to Github actions, and split into two workflows:

• Checks: npm run test and validations
• Release: npm run build and npm run release