• bump Loki – new version of Loki has a much better output and it appears to be faster (I had serious problems with speed 😬)
• update visual references – I carefully updated them to remove code blocks and check for visual regressions, so now references are fully up-to-date
• add missing references – let's hope this works out now for everyone 🤞
• add npm scripts to make testing easier
• remove unused dotenv dependency (unrelated)

Closes: #2293

We should probably switch to Git LFS eventually, I've never used it, though.<br/><br/><br/><url>LiveURL: https://orbit-test-update-visual-references.surge.sh</url>

Bumps loki from 0.15.1 to 0.25.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/oblador/loki/releases">loki's releases</a>.</em></p> <blockquote> <h2>0.24.0</h2> <h2>New functionality</h2> <ul> <li>Async CSF stories are now supported via the <code>@loki/create-async-callback</code> package.</li> <li><code>chromeSelector</code> option can now be passed on a per story basis via the loki parameter.</li> </ul> <h2>Fixes</h2> <ul> <li>Better support for <code>chromeSelector</code> option not ending with <code>> *</code> .</li> </ul> <h2>0.23.0</h2> <h2>Breaking changes</h2> <ul> <li><strong>Support skip via story parameters</strong>. This deprecates support for SB < 5.</li> <li><strong>Bump default chrome docker version to 85</strong>. This will change how the default font renders, if you want to keep the old version, use <code>--chromeDockerImage yukinying/chrome-headless:63.0.3230.2</code>.</li> </ul> <h2>0.22.1</h2> <h3>Bug fixes</h3> <ul> <li>Fix loki global check for React Native</li> </ul> <h2>0.22.0</h2> <h3>New functionality</h3> <ul> <li><code>isLokiRunning</code> function in the <code>@loki/is-loki-running</code> package that will return <code>true</code> during a test run. This is useful to disable things causing flakiness, such as JavaScript animations or GIFs that aren't automatically disabled by loki.</li> </ul> <h2>0.21.0</h2> <h2>Breaking changes</h2> <ul> <li>Improve getSelectorBoxSize to find fixed & absolute elements. This is a bug fix, but will alter the cropping of some stories, especially those using fixed and absolute elements.</li> </ul> <h2>Bug fixes</h2> <ul> <li>Listen to requests until selector is present, fixes flakiness with fonts for slow components/big bundles</li> <li>Make blinking input carets transparent to avoid flakiness</li> </ul> <h2>0.20.2</h2> <ul> <li>Add compatibility with Storybook 5 in <code>loki init</code> command</li> <li>Pass through third <code>storiesOf</code> param</li> <li>Disable pointer events to combat unintended <code>:hover</code> styles</li> <li>Add loki command alias to entry package for <code>yarn add global</code> support</li> <li>Wait between retries when launching stories tab to combat flakiness in Circle CI</li> </ul> <h2>0.20.1</h2> <h2>Bug fixes</h2> <ul> <li>Fix bug where <code>looks-same</code> differ would not properly detect changes.</li> </ul> <h2>0.20.0</h2> <h2>New features</h2> <ul> <li>New <code>fileNameFormatter</code> config enabling any custom file format of snapshot files.</li> <li>Support separate configuration file, as <code>.lokirc</code> or <code>loki.config.js</code>.</li> </ul> <h2>Bug fixes</h2> <ul> <li>Fix bad file reference in <code>react-native</code> integration</li> </ul> <h2>0.19.1</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/oblador/loki/commit/d3e785830d395319e61d8f824215d86f439c995c"><code>d3e7858</code></a> v0.25.1</li> <li><a href="https://github.com/oblador/loki/commit/6c88b9c3d9f3e9d7faa83ac8681df398994d47b5"><code>6c88b9c</code></a> v0.25.0</li> <li><a href="https://github.com/oblador/loki/commit/ed0d902e2c13a913d28b6c97fb360742385f6073"><code>ed0d902</code></a> Add maintainers section to README (<a href="https://github.com/oblador/loki/tree/HEAD/packages/loki/issues/259">#259</a>)</li> <li><a href="https://github.com/oblador/loki/commit/ae70705a46e834d34f15862faa74dfc35f3a28c0"><code>ae70705</code></a> v0.24.0</li> <li><a href="https://github.com/oblador/loki/commit/77bbcf3ef7aac4b65ef54a270077766ac4274a33"><code>77bbcf3</code></a> Use show test badge from github actions</li> <li><a href="https://github.com/oblador/loki/commit/77b117d9b8d92756a7be6085eaae967ba9c4531c"><code>77b117d</code></a> Remove version in node requirement (<a href="https://github.com/oblador/loki/tree/HEAD/packages/loki/issues/257">#257</a>)</li> <li><a href="https://github.com/oblador/loki/commit/510fd0501e27efde006d906b60a0cf1e41c49015"><code>510fd05</code></a> v0.23.0</li> <li><a href="https://github.com/oblador/loki/commit/69ca523e0c2384b342c1682ac79e0ab4c1699ee1"><code>69ca523</code></a> v0.22.1</li> <li><a href="https://github.com/oblador/loki/commit/0afc976871107720e6eddcf70f5a582a9dc958b0"><code>0afc976</code></a> v0.22.0</li> <li><a href="https://github.com/oblador/loki/commit/c7429d38b5155d825994ca0cde445c1009b1a9f3"><code>c7429d3</code></a> v0.21.1</li> <li>Additional commits viewable in <a href="https://github.com/oblador/loki/commits/v0.25.1/packages/loki">compare view</a></li> </ul> </details> <br />

You can trigger a rebase of this PR by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details><br/><br/><br/><url>LiveURL: https://orbit-dependabot-npm-and-yarn-loki-0-25-1.surge.sh</url>

• bump Loki – new version of Loki has a much better output and it appears to be faster
• update visual references – I carefully updated them to remove code blocks and check for visual regressions, so now everything is good
• add missing references – let's hope this works out now for everyone 🤞
• add npm scripts to make testing easier
• remove unused dotenv dependency (unrelated)

We should probably switch to Git LFS or something, I've never used it, though.

That's true, it's kinda standalone currently, but try applying to it everything that isn't specifically Flow-related so we see what happens. When we start adding TypeScript files at some point in the future, we want to have the same ESLint support as we did for Flow files.

Same as Inline. Considering that we have larger tokens, maybe we can just use those? Or maybe it will set off some kind of bomb, only Filip knows the reason behind this 😅

Best to wrap text content in all of these stories in the Text component, just to get rid of that nasty Times New Roman.

Spelling:

    const getOmitted = hex =>

Instead of fetching getComponentStyle and checking for properties, you can also use toHaveStyle. In this case I recommend the object syntax:

expect(el).toHaveStyle({ color: getOmitted(theme.orbit.paletteBlueDark) })

Same thing, basically, but reads better.

Also, just to point out that these three sizes are mapped to the same token.

This looks like a placeholder, you can copy the description used by some components:

      info: "You can try all possible configurations of this component. However, check Orbit.Kiwi for more detailed design guidelines.",

Complete release workflow:

1. create .env file with GH_TOKEN (only once)
2. create PR with fixed Loki tests
3. run yarn publish-packages (publish is reserved), this will do everything, including git push I believe<br/><br/><br/><url>LiveURL: https://orbit-improve-release-script.surge.sh</url>

closes #2346 (again)

related to #2389

This Pull Request meets the following criteria:

• [x] Tests have been added/adjusted for my new feature
• [x] New Components are registered in index.js of my project <br/><br/><br/><url>LiveURL: https://orbit-sampi-fix-2346.surge.sh</url>

@vepor removed yarn autoclean, it's a good thing you noticed!

• chore: fix clashing types in TypeScript
• chore: simplify TypeScript configuration
• ci: start type checking with TypeScript <br/><br/><br/><url>LiveURL: https://orbit-test-typescript.surge.sh</url>

Just rebased to fix conflicts.

Oh… I thought that if an old version is being loaded, then static revisioning isn't set up correctly because the cache was supposed to be busted. That's a terrifying idea to me as an author that someone loads an old CSS or JS file, I guess things will break for them either way? 🤔

This clean task was not only for deleting old assets, but deleting old anything. Old pages etc. I want a 404 page to appear when a page has been deleted. But I'll remove this task since we're focusing on revisioning only here.

I would like to avoid this, too, but, as I said, I need help. 🙏

Also, nothing happens because I forgot to add tasks to them, so they are completely useless 😆

Ok, I'll give it a shot.

If we're removing watching (which I will), then it doesn't.

Could you be more specific? I never used it before.

<br/><br/><br/><url>LiveURL: https://orbit-improve-check-icons-cli.surge.sh</url>

This Pull Request meets the following criteria:

• [ ] Tests have been added/adjusted for my new feature
• [ ] New Components are registered in index.js of my project

I figured it out! 🚀 I needed to add .yarnclean to hash files because CI should rebuild dependencies when contents of .yarnclean change. CI was failing simply because yarn install didn't run, so @types/react-native was still there.

If you agree, I the old Dependabot needs to be disabled in the web app.

Damnit, for some reason .yarnclean doesn't automatically trigger Yarn, I had to run yarn autoclean --force the first time, then it started doing it on its own.

Make sure to rebase, not squash, if you're merging.

• chore: fix clashing types in TypeScript
• chore: simplify TypeScript configuration
• ci: start type checking with TypeScript

Bumps typescript from 3.9.7 to 4.0.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Microsoft/TypeScript/releases">typescript's releases</a>.</em></p> <blockquote> <h2>TypeScript 4.0.3</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-0/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+4.0.0%22+is%3Aclosed+">fixed issues query for TypeScript v4.0.0 (Beta)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+4.0.1%22+is%3Aclosed+">fixed issues query for TypeScript v4.0.1 (RC)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+4.0.2%22+is%3Aclosed+">fixed issues query for TypeScript v4.0.2</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+4.0.3%22+is%3Aclosed+">fixed issues query for TypeScript v4.0.3</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript-40">Visual Studio 2017/2019</a> (<a href="https://github.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017">Select new version in project options</a>)</li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> <h2>TypeScript 4.0</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-0/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+4.0.0%22+is%3Aclosed+">fixed issues query for TypeScript v4.0.0 (Beta)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+4.0.1%22+is%3Aclosed+">fixed issues query for TypeScript v4.0.1 (RC)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+4.0.2%22+is%3Aclosed+">fixed issues query for TypeScript v4.0.2</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript-40">Visual Studio 2017/2019</a> (<a href="https://github.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017">Select new version in project options</a>)</li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> <h2>TypeScript 4.0 Beta</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-4-0-beta/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+4.0%22+is%3Aclosed+">fixed issues query for Typescript v4.0-beta</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://marketplace.visualstudio.com/items?itemName=TypeScriptTeam.TypeScript-40beta">Visual Studio 2017/2019</a> (<a href="https://github.com/Microsoft/TypeScript/wiki/Updating-TypeScript-in-Visual-Studio-2017">Select new version in project options</a>)</li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/TypeScript/commit/fee3bfbe91b7582f42e2f49814b87353f67e63f4"><code>fee3bfb</code></a> Bump version to 4.0.3 and LKG</li> <li><a href="https://github.com/microsoft/TypeScript/commit/2eb5deae4bafe169ec1d2ecf66999003574164bb"><code>2eb5dea</code></a> Update LKG</li> <li><a href="https://github.com/microsoft/TypeScript/commit/1dde4bbe4ebc7fb210bf124b9590a82573a49806"><code>1dde4bb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/40595">#40595</a> from typescript-bot/pick/39924/release-4.0</li> <li><a href="https://github.com/microsoft/TypeScript/commit/23c77c4e329ee3a27c4dfe7d9f6905aca12281b0"><code>23c77c4</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/40444">#40444</a> from amcasey/Cherry40043</li> <li><a href="https://github.com/microsoft/TypeScript/commit/e3301f7294c759be4141f4a49b691fe2614f93ef"><code>e3301f7</code></a> Cherry-pick PR <a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/39924">#39924</a> into release-4.0</li> <li><a href="https://github.com/microsoft/TypeScript/commit/65b84e707e118b802ad41ca164debd15f4915a95"><code>65b84e7</code></a> Cherry-pick PR <a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/40273">#40273</a> into release-4.0 (<a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/40303">#40303</a>)</li> <li><a href="https://github.com/microsoft/TypeScript/commit/657576ae7c9da142bdbbe43e64d425fa292124fe"><code>657576a</code></a> Set stackTraceLimit to 0 in fileSystemEntryExists</li> <li><a href="https://github.com/microsoft/TypeScript/commit/3e7a8e7e45aed722d7955e35e9fbac14ea75958a"><code>3e7a8e7</code></a> Cherry-pick PR <a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/40348">#40348</a> into release-4.0 (<a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/40349">#40349</a>)</li> <li><a href="https://github.com/microsoft/TypeScript/commit/8890dcb7ca81857678b110a1586f3642d1447ee2"><code>8890dcb</code></a> Cherry-pick PR <a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/40118">#40118</a> into release-4.0 (<a href="https://github-redirect.dependabot.com/Microsoft/TypeScript/issues/40134">#40134</a>)</li> <li><a href="https://github.com/microsoft/TypeScript/commit/912cbdfcb6b5ed1b0623390fc350c3c313fc8f1b"><code>912cbdf</code></a> Update LKG</li> <li>Additional commits viewable in <a href="https://github.com/Microsoft/TypeScript/compare/v3.9.7...v4.0.3">compare view</a></li> </ul> </details> <br />

You can trigger a rebase of this PR by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details><br/><br/><br/><url>LiveURL: https://orbit-dependabot-npm-and-yarn-typescript-4-0-3.surge.sh</url>

<br/><br/><br/><url>LiveURL: https://orbit-fix-timeline.surge.sh</url>

Ok!

closes #2368

This Pull Request meets the following criteria:

• [x] Tests have been added/adjusted for my new feature
• [x] New Components are registered in index.js of my project

remove internal dependency (it will use it anyway, but won't affect version bumps)

<br/><br/><br/><url>LiveURL: https://orbit-sampi-fix-2368.surge.sh</url>

@kiwicom/babel-plugin-orbit-components always gets a version bump because it has @kiwicom/orbit-components in devDependencies. It will probably be enough to remove it, otherwise we should consider removing all devDependencies from both packages.

Success can be checked by running yarn release, then seeing whether the version is unjustifiably bumped.

lerna/lerna#1737

Bumping devDependencies also bumps the version, as we've found out, so it's most likely best to move them all to the root package.json. The added benefit is that way we avoid having to bump the same development dependency in multiple places. I think it will be easier to manage the monorepo this way.

Also, I would recommend to rebase and check for ESLint errors, just in case.