-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for additional public folders #5
Comments
Implemented. |
ndelangen
added a commit
that referenced
this issue
Apr 5, 2017
Merge branch 'master' of github.com:storybooks/react-storybook
ndelangen
pushed a commit
that referenced
this issue
Apr 16, 2019
ndelangen
pushed a commit
that referenced
this issue
Apr 16, 2019
ndelangen
pushed a commit
that referenced
this issue
Apr 16, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 17, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 17, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 17, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 18, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 18, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 18, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 18, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 18, 2019
leoyli
pushed a commit
that referenced
this issue
Apr 18, 2019
gaetanmaisse
added a commit
that referenced
this issue
Apr 26, 2020
…all issue When Yarn 2 is trying to install and patch TS 3.6 it throws: ➤ YN0013: │ typescript@patch:typescript@npm%3A3.6.5#builtin<compat/typescript>::version=3.6.5&hash=c79188 can't be found in the cache and will be fetched from the disk ➤ YN0001: │ Error: typescript@patch:typescript@npm%3A3.6.5#builtin<compat/typescript>::version=3.6.5&hash=c79188: Cannot apply hunk #5 This is a Yarn 2 related issue, tracked here: yarnpkg/berry#1221
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is to support loading static files via a folder.
The text was updated successfully, but these errors were encountered: