sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: Typescript install after create app: not created tsconfig.js and so
Labels: needs triage,issue: bug report


### Describe the bug

I follow this steps https://create-react-app.dev/docs/adding-typescript but the Typescript support was not activated and I did'nt found any tsconfig.
Why?

### Did you try recovering your dependencies?

<!--
  Your module tree might be corrupted, and that might be causing the issues.
  Let's try to recover it. First, delete these files and folders in your project:

    * node_modules
    * package-lock.json
    * yarn.lock

  Then you need to decide which package manager you prefer to use.
  We support both npm (https://npmjs.com) and yarn (http://yarnpkg.com/).
  However, **they can't be used together in one project** so you need to pick one.

  If you decided to use npm, run this in your project directory:

    npm install -g npm@latest
    npm install

  This should fix your project.

  If you decided to use yarn, update it first (https://yarnpkg.com/en/docs/install).
  Then run in your project directory:

    yarn

  This should fix your project.

  Importantly, **if you decided to use yarn, you should never run `npm install` in the project**.
  For example, yarn users should run `yarn add <library>` instead of `npm install <library>`.
  Otherwise your project will break again.

  Have you done all these steps and still see the issue?
  Please paste the output of `npm --version` and/or `yarn --version` to confirm.
-->

Yes. Any result.
b
### Environment

<!--
  To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required.
  This enables the maintainers quickly reproduce the issue and give feedback.

  Run the following command in your React app's folder in terminal.
  Note: The result is copied to your clipboard directly.

  `npx create-react-app --info`

  Paste the output of the command in the section below.
-->

 System:
    OS: macOS 11.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
  Binaries:
    Node: 12.18.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.10 - /usr/local/bin/npm
  Browsers:
    Chrome: 87.0.4280.88
    Edge: 87.0.664.52
    Firefox: 84.0.1
    Safari: 14.0.2
  npmPackages:
    react: ^17.0.1 => 17.0.1 
    react-dom: ^17.0.1 => 17.0.1 
    react-scripts: 4.0.1 => 4.0.1 
  npmGlobalPackages:
    create-react-app: Not Found
Repository: pytorch
Issue: Find the joint eigenvalue of two matrices. 
Labels: feature,triaged,needs research,module: linear algebra

## 🚀 Feature
A differentiable function to find the joint eigenvalues of two matrices, MATLAB has a built-in function to find the joint eigenvalues, but I'm not sure whether it is differentiable. 
https://stackoverflow.com/questions/36551182/how-can-i-find-the-joint-eigenvalues-of-two-matrices-in-matlab

## Motivation
I encounter this problem when I want to use a distance measure for covariance matrices as the loss function, the calculation of which requires the joint eigenvalues of two matrices. 
![image](https://user-images.githubusercontent.com/39657051/103912298-12cc4380-5142-11eb-8ed1-18f5d9b618ac.png)

## Pitch
I find the function torch.lobpcg might be able to find the joint eigenvalues (but only upto k-largest) and the backward is about to break (https://github.com/pytorch/pytorch/issues/38948).
Could pytorch team implement a function to find the joint eigenvalues of two matrices which is differentiable?

## Alternatives
I'm way to layman for this level linear algebra, but I found this might be a related work-around.
https://www.alglib.net/eigen/symmetric/generalizedsymmevd.php

## Additional context


cc @jianyuh @nikitaved @pearu @mruberry @heitorschueroff @walterddr @IvanYashchuk
Repository: rust
Issue: There's no flag to allow assert_eq to format as multi-line results
Labels: C-enhancement,A-error-handling,T-libs,A-fmt

I think this is a `bug`, rather than a feature request, but maybe others will disagree - it certainly feels like a UX missed opportunitiy.

Looking at the `assert_eq` code, we *always* debug format on one line despite us having the ability to nicely format as multi-line.

https://doc.rust-lang.org/src/core/macros/mod.rs.html#48-49

Given that IDEs like intellirust have really nice diff viewers to show the difference between expected and actual it would be great if a flag could be set to allow expected and actual to be printed using the mutliline debug formatter.
(I've shown how TeamCity can show similar test output diffs on their website using a crate I rolled called `cargo-service-message`)

It's a small change but it would greatly improve the usability in more complex situations. I would keep single line as default, but having a multiline option would really improve test reporting.

Ultimately nothing building on top can do anything nice unless we find a way to format as {:#?}, so we really need to find a way to enable this as an option.
Repository: go
Issue: cmd/pprof: provide help page
Labels: Documentation,NeedsInvestigation,compiler/runtime

The pprof tool helpfully provides a `-http` flag that opens a web page with an interactive view, but there's no easy way of telling what elements of the UI mean or do. For example, it would be useful to have a key to the diagrams to say what the numbers mean and what's the difference between a dotted and a solid line, etc.

As it is, the user is left to google for potentially relevant articles blog posts that might or might not be out of date now.

At the very least, a link to an online documentation page would be good, although that might suffer from potential version skew if the URL isn't versioned.
Repository: ant-design
Issue: Change responsive List grid dynamically
Labels: Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/responsive-grid-list-antd4100-forked-ob5sw)

### Steps to reproduce
Add button to change List grid property. The grid property must be responsive.

### What is expected?
The grid should change from 3 columns to 2 columns or vise versa when the button is clicked.

### What is actually happening?
The columns do not change.

| Environment | Info |
|---|---|
| antd | 4.10.0 |
| React | react version 17.0.1 |
| System | Windows 10 Pro Version 10.0.19041 |
| Browser | Chrome Version 87.0.4280.88 |

---
When using a responsive List grid you can't change it dynamically, such as using a button click to change the number of columns. Using a non-responsive grid works.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: create-react-app
Issue: webpackChunkName not being honored by CRA when dynamically importing vendor code
Labels: stale,needs triage,issue: bug report

### Describe the bug

When writing the below:
```javascript
import(/* webpackChunkName: "lodash" */ 'lodash').then(() => {
  console.log('Loaded lodash');
})
```

The imported code does get chunked separately, but the name specified in the webpack magic comment isn't honored in the production build (the chunk is still named `[number].[hash].chunk.js`). Interestingly, the magic comments do work for dynamic imports pointing to app code (as opposed to vendor code, e.g. `import(/* webpackChunkName: "test" */ './test')`).

### Did you try recovering your dependencies?

Yes

### Which terms did you search for in User Guide?

webpackChunkName

### Environment

current version of create-react-app: 4.0.1
running from /Users/guillaumedupuy/.npm/_npx/60415/lib/node_modules/create-react-app

System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
  Binaries:
    Node: 14.15.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.8 - /usr/local/bin/npm
  Browsers:
    Chrome: 87.0.4280.141
    Edge: Not Found
    Firefox: 84.0.1
    Safari: 14.0
  npmPackages:
    react: ^17.0.1 => 17.0.1 
    react-dom: ^17.0.1 => 17.0.1 
    react-scripts: 4.0.0 => 4.0.0 
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to reproduce

See https://github.com/guidupuy/test-project

Run `npm run build`

### Expected behavior

Going into `/build/static/js`, I should see a file named `lodash.[hash].chunk.js` with the lodash source code.

### Actual behavior

Instead, I see a file named `3.[hash].chunk` with the lodash source code.
Repository: pytorch
Issue: torch.float_power out= and inplace variant errors on non-matching output dtype instead of casting
Labels: triaged,module: type promotion

## 🐛 Bug

Operators usually check that the computation type can be safely casted to the output (and this matches NumPy behavior), and this doesn't happen with `float_power`.

```
>>> torch.float_power(torch.randn(2,3), 5., out=torch.randn(2,3))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: output type Floatis not the desired output type Double
>>> torch.randn(2,3).float_power_(5.)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: self tensor type Floatis not the desired type Double
>>> np.float_power(np.random.randn(2,3).astype(np.float32), 5., out=np.random.randn(2,3).astype(np.float32))
array([[-1.1256918e-01,  5.3110137e+00, -3.6077526e+01],
       [-1.2552988e-02, -3.9551861e-04,  2.7541189e+01]], dtype=float32)
```

this violates https://github.com/pytorch/pytorch/wiki/Developer-FAQ#how-does-out-work-in-pytorch

```
Collecting environment information...
PyTorch version: 1.8.0.dev20201222
Is debug build: False
CUDA used to build PyTorch: 9.2
ROCM used to build PyTorch: N/A

OS: CentOS Linux 7 (Core) (x86_64)
GCC version: (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Clang version: Could not collect
CMake version: version 3.14.0

Python version: 3.7 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: Tesla M40
GPU 1: Tesla M40

Nvidia driver version: 418.126.02
cuDNN version: /usr/local/cuda-9.2/targets/x86_64-linux/lib/libcudnn.so.7.4.2
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip] numpy==1.18.1
[pip] pytorch-lightning==0.9.0
[pip] torch==1.8.0.dev20201222
[pip] torchaudio==0.8.0a0+1398187
[pip] torchvision==0.9.0.dev20201222
[conda] blas                      1.0                         mkl
[conda] cudatoolkit               9.2                           0
[conda] mkl                       2020.1                      217
[conda] mkl-include               2020.1                      217
[conda] mkl-service               2.3.0            py37he904b0f_0
[conda] mkl_fft                   1.0.14           py37ha843d7b_0
[conda] mkl_random                1.1.0            py37hd6b4f25_0
[conda] numpy                     1.18.1           py37h4f9e942_0
[conda] numpy-base                1.18.1           py37hde5b4d6_1
[conda] pytorch                   1.8.0.dev20201222 py3.7_cuda9.2.148_cudnn7.6.3_0    pytorch-nightly
[conda] pytorch-lightning         0.9.0                     <pip>
[conda] torch                     1.8.0.dev20201130+cpu           <pip>
[conda] torchaudio                0.8.0.dev20201130           <pip>
[conda] torchaudio                0.8.0.dev20201222            py37    pytorch-nightly
[conda] torchvision               0.9.0.dev20201222       py37_cu92    pytorch-nightly
```

cc @nairbv @mruberry
Repository: flutter
Issue: [canvaskit]: switch to the official shadow bounds estimator
Labels: engine,platform-web,c: rendering,e: web_canvaskit,P2,team-web,triaged-web

We currently use a home-grown algorithm for estimating shadow bounds. There's risk that our algorithm gets it wrong and causes rendering issues. When https://bugs.chromium.org/p/skia/issues/detail?id=11146 is available we should switch to the official shadow bounds estimator.
Repository: flutter
Issue: --asan not working on Android targets
Labels: engine,dependency: fuchsia,P2,c: tech-debt,team-engine,triaged-engine

Failures like:

```
[201/3613] CXX obj/third_party/icu/source/common/icuuc.uenum.o
FAILED: obj/third_party/icu/source/common/icuuc.uenum.o 
/Users/dnfield/goma/gomacc ../../buildtools/mac-x64/clang/bin/clang++ -MD -MF obj/third_party/icu/source/common/icuuc.uenum.o.d -DU_COMMON_IMPLEMENTATION -DU_ICUDATAENTRY_IN_COMMON -DUSE_OPENSSL=1 -DUSE_OPENSSL_CERTS=1 -DADDRESS_SANITIZER -DANDROID -DHAVE_SYS_UIO_H -D__compiler_offsetof=__builtin_offsetof -Dnan=__builtin_nan -D_LIBCPP_DISABLE_AVAILABILITY=1 -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCPP_ENABLE_THREAD_SAFETY_ANNOTATIONS -D_DEBUG -DHAVE_DLOPEN=0 -DUCONFIG_ONLY_HTML_CONVERSION=1 -DUCONFIG_USE_WINDOWS_LCID_MAPPING_API=0 -DU_CHARSET_IS_UTF8=1 -DU_USING_ICU_NAMESPACE=0 -DU_ENABLE_DYLOAD=0 -DUSE_CHROMIUM_ICU=1 -DU_ENABLE_TRACING=1 -DU_ENABLE_RESOURCE_TRACING=0 -DU_STATIC_IMPLEMENTATION -DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_FILE -DUCHAR_TYPE=uint16_t -I../.. -Igen -I../../third_party/libcxx/include -I../../third_party/libcxxabi/include -I../../third_party/libcxxabi/include -I../../third_party/icu/source/common -I../../third_party/icu/source/i18n -fno-strict-aliasing -fno-omit-frame-pointer -gline-tables-only -fsanitize=address -fPIC -pipe -fcolor-diagnostics -ffunction-sections -funwind-tables -fno-short-enums -nostdinc++ -mllvm\ -asan-globals=0 --target=aarch64-linux-android -isystem../../third_party/android_tools/ndk/sources/android/support/include -isystem../../third_party/android_tools/ndk/sysroot/usr/include/aarch64-linux-android -D__ANDROID_API__=22 -fvisibility=hidden --sysroot=/Users/dnfield/src/flutter/engine/src/third_party/android_tools/ndk/sysroot -Wstring-conversion -Wnewline-eof -O0 -g2 -Wendif-labels -Werror -Wno-missing-field-initializers -Wno-unused-parameter -Wno-implicit-int-float-conversion -Wno-c99-designator -Wno-non-c-typedef-for-linkage -Wno-deprecated-copy -Wno-range-loop-construct -Wno-unused-function -Wno-parentheses -Wno-unused-function -Wno-unused-variable -Wno-deprecated-declarations -fvisibility-inlines-hidden -std=c++17 -nostdinc++ -nostdinc++ -fno-exceptions   -c ../../third_party/icu/source/common/uenum.cpp -o obj/third_party/icu/source/common/icuuc.uenum.o
clang-11: error: unknown argument: '-mllvm -asan-globals=0'
```

when doing:

`./flutter/tools/gn --android --android-cpu arm64 --runtime-mode profile --no-lto --asan`
Repository: rust
Issue: Add option to pass environment variables to rustc with a flag
Labels: T-compiler,C-feature-request

See #78913 for more background.

I'm a meson developer, working to make rust work better with meson. I know that cargo is the official build system for rust, but for me and the projects I work on cargo is unacceptable, we have a *massive* C/C++ codebase already using meson, with interest in migrating some (but not all) of our code to rust. Mostly things work fine, but one problem we do have is including generated code.

Cargo handles generated code by setting an `OUT_DIR` environment variable, this works for cargo because it has a number of unique design decisions compared to most build systems. For Cmake and meson and particular this is problematic because we generate a declarative build system which the user invokes, visual-studio, ninja, make, etc; so there are separate "configure" and "build" stages. For ninja in particular environment variables are problematic because it's made an explicit design choice not to support them. As such, we have no way to set environment variables at build time without resorting to something ugly like wrapping rustc in a script to proxy the variables.

What would be nice is the ability to pass environment variables to rustc directly, much like `--cfg`, something like `--env "OUT_DIR=/some/dir"`. This would allow us to make `include()` work like cargo, but without needing to resort to wrapping rustc and making things slower than they need to be.
Repository: PowerToys
Issue: Audit pen & touch interaction works on top of just mouse
Labels: Issue-Bug,Planning-Consideration

All PowerToys should work with the touch and pen, not only mouse.  #8975 is prompting this

Any new issue should be logged.

## Touch
- [ ] Settings
- [ ] Color picker - https://github.com/microsoft/PowerToys/issues/10854
- [ ] FancyZones Editor
- [ ] FancyZone
- [ ] SVG Preview pane
- [ ] Markdown Preview pane
- [ ] Image Resizer
- [ ] Keyboard Manager - https://github.com/microsoft/PowerToys/issues/9748
- [ ] PowerRename
- [ ] PowerToys Run
- [ ] Shortcut Guide

## Pen
- [ ] Settings
- [ ] Color picker - https://github.com/microsoft/PowerToys/issues/10854
- [ ] FancyZones Editor
- [ ] FancyZone
- [ ] SVG Preview pane
- [ ] Markdown Preview pane
- [ ] Image Resizer
- [ ] Keyboard Manager
- [ ] PowerRename
- [ ] PowerToys Run
- [ ] Shortcut Guide
Repository: opencv
Issue: OpenCVModules.cmake has wrong libraries on static windows, static standalone IPP
Labels: priority: low,category: build/install,RFC

opencv built on windows, building *static opencv* libraries, with *standalone* IPP, with IPP *static* libraries creates wrong downstream CMake package files -- those files that are later included in applications that build with opencv as a library. These downstream package files fail to have the needed `mt` at the end of the library name.

These package files are created when OpenCV is built/installed. They declare a list of libraries to be linked and downstream apps that are built with cmake use that list when `find_package(opencv)...target_link_libraries(${OpenCV_LIBS})` etc. is used. That list is incorrect. The errant list is `ippi`, `ippcv`, etc. The correct list is `ippimt`, `ippcvmt`, etc.

Easy fix with PR I have ready.

##### System information (version)
- OpenCV => 4.5.1
- Operating System / Platform => Microsoft Windows [Version 10.0.19042.685] 64-bit
- Compiler => Visual Studio 2019 Community v16.8.3

##### Steps to reproduce

1. Setup build machine as a describe above
2. `With_IPP=ON`, `IPPROOT=xxxx`, `BUILD_WITH_DYNAMIC_IPP=OFF`, `BUILD_IPP_IW=OFF`, `BUILD_SHARED_LIBS=OFF`
3. Build opencv
4. install
5. inspect `install/Release/x64/vc16/staticlib/OpenCVModules.cmake`
6. (Optional) create downstream application with cmake that uses opencv and ipp functionality. Try to build that application.

You will see incorrect libraries listed in (5). And a build of a downstream application will fail with libraries not found with (6)

```
INTERFACE_LINK_LIBRARIES ...$<LINK_ONLY:ippcv>;\$<LINK_ONLY:ippi>;\$<LINK_ONLY:ippcc>;
```

The correct list is

```
INTERFACE_LINK_LIBRARIES ...$<LINK_ONLY:ippcvmt>;\$<LINK_ONLY:ippimt>;\$<LINK_ONLY:ippccmt>;
```

##### Issue submission checklist

 - [X] I report the issue, it's not a question
 - [X] I checked the problem with documentation, FAQ, open issues,
       answers.opencv.org, Stack Overflow, etc and have not found solution
 - [X] I updated to latest OpenCV version and the issue is still there
Repository: pytorch
Issue: `requires_grad_` in `no_grad` context returns incorrect value with tensor subclasses
Labels: module: autograd,triaged

## 🐛 Bug

When `requires_grad_` is called in a `no_grad` context on a `Tensor`, it returns the newly set value correctly. However, when called on subclasses, it incorrectly returns the old value.

## To Reproduce

Steps to reproduce the behavior:

This prints the correct values `False True True`:

```python
x = Tensor(torch.rand(4,3,16,16))
with torch.no_grad():
    before = x.requires_grad
    y = x.requires_grad_()
    print(before, y.requires_grad, x.requires_grad)
```

This incorrectly prints `False` as the second value:

```python
class FooTensor(Tensor): pass
x = FooTensor(torch.rand(4,3,16,16))
with torch.no_grad():
    before = x.requires_grad
    y = x.requires_grad_()
    print(before, y.requires_grad, x.requires_grad)
```

## Expected behavior

`False True True` should be printed.

## Environment


```
Collecting environment information...
PyTorch version: 1.7.1
Is debug build: False
CUDA used to build PyTorch: 11.0
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.1 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: 7.0.0 (https://github.com/apple/swift-clang.git 0e8e8c3f4790ab55cacb0388571fecbdd2627e6b)85bad068f01)
CMake version: version 3.16.3

Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: TITAN RTX
GPU 1: TITAN RTX
GPU 2: TITAN RTX
GPU 3: TITAN RTX
GPU 4: TITAN RTX
GPU 5: TITAN RTX
GPU 6: TITAN RTX

Nvidia driver version: 455.45.01
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.4
/usr/local/cuda-10.0/lib64/libcudnn.so.7.6.1
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.19.4
[pip3] pytorch-ignite==0.4.2
[pip3] pytorch-lightning==1.1.3
[pip3] torch==1.7.1
[pip3] torchvision==0.8.2
[conda] blas                      2.16                        mkl    conda-forge
[conda] cudatoolkit               11.0.221             h6bb024c_0    fastchan
[conda] libblas                   3.8.0                    16_mkl    conda-forge
[conda] libcblas                  3.8.0                    16_mkl    conda-forge
[conda] liblapack                 3.8.0                    16_mkl    conda-forge
[conda] liblapacke                3.8.0                    16_mkl    conda-forge
[conda] mkl                       2020.2                      256
[conda] numpy                     1.19.4           py38h18fd61f_2    conda-forge
[conda] pytorch                   1.7.1           py3.8_cuda11.0.221_cudnn8.0.5_0    fastchan
[conda] pytorch-ignite            0.4.2                    pypi_0    pypi
[conda] pytorch-lightning         1.1.3                    pypi_0    pypi
[conda] torchvision               0.8.2                py38_cu110    fastchan
```


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer
Repository: go
Issue: cmd/dist: ensure consistency between (*tester).supportedBuildmode and cmd/internal/sys.BuildModeSupported
Labels: Testing,NeedsInvestigation

`(*cmd/dist.tester).supportedBuildmode` contains a large switch that determines whether a given buildmode is supported for a given `GOOS`/`GOARCH`:
https://github.com/golang/go/blob/fa90aaca7d523eaf81c02b48a412cad4ebc57817/src/cmd/dist/test.go#L977-L1038

That switch nearly exactly duplicates the one in [`cmd/internal/sys.BuildModeSupported`](https://tip.golang.org/cmd/internal/sys/#BuildModeSupported), which was itself extracted from a portion of [`cmd/go/internal/work.buildModeInit`](https://tip.golang.org/cmd/go/internal/work/?m=all#buildModeInit).

`cmd/dist` should be changed to use (instead of duplicating) the function from `cmd/internal/sys`.
Repository: storybook
Issue: Duplicate content in Google because iframe url gets indexed
Labels: bug,core

**Describe the bug**
When searching Google for content inside of Storybook, pages appear twice in the search results. I believe this is because Google indexes the Storybook URL for a given story _and_ the preview iframe url (which contains the same content). 

**To Reproduce**
Steps to reproduce the behavior:

1. Go to this [search results page](https://www.google.com/search?ei=2Gn3X-WMC4iS0PEP1KKN0AI&q=recruitee+storybook+accessibility&oq=recruitee+storybook+acces&gs_lcp=CgZwc3ktYWIQAxgAMgcIIRAKEKABMgcIIRAKEKABMgcIIRAKEKABMgcIIRAKEKABOgQIABBHOgUIIRCgAToFCCEQqwJQyzdY7D9gw0loAHACeACAAZsBiAHTBpIBAzAuNpgBAKABAaoBB2d3cy13aXrIAQjAAQE)
2. Look at top two links
3. See that the content is identical but one is the iframe and the other is the full Storybook

**Expected behavior**
That the iframe URL does not appear in the index _or_ has a canonical link to the Storybook URL.

**Screenshots**
![image](https://user-images.githubusercontent.com/263385/103940343-2902e100-50fb-11eb-8c08-d8e07cdf3330.png)