Issue summary

The Sketch file is a thing of beauty. Thank you for the hard work and inspiration.

Would love to see some more consistency in the spacings.

☝️ is just one example but found a handful of others.

Would also love to see some guidance as to the grids and guides used. At times spacing was a factor of 10px other times they were factors of 8px.

• Polaris version: v1.0.0
• Sketch version: 43.2
• Device: Mac
• Operating System: macOS Sierra

Issue summary

• License file missing from the root of the project.
• License type missing from the package.json file.

Expected behavior

LICENSE.md

When there is a LICENSE.md file on the root of the repository, GitHub will show the type of license for users and search engines. It will also help 3rd party tools like to figure out the type of license via The Licenses API of GitHub.

GitHub repository's license is displayed on the top right corner of the info bar:

More details from GitHub's User Documentation: Licensing a repository

package.json

It would also make sense to add right license type to the package.json file. This is important, because it will allow tools to automatically validate whether license is compatible with requirements or not.

  "license": "MIT",

More detailed description about "license": structure (and accepted license types).

Actual behavior

License file is not found from the Git repository, so the UI of GitHub is not displaying it for the potential users.

Missing license from the package.json file makes it difficult to automatically verify the license type:

  "license": "SEE LICENSE IN README.md",

Steps to Reproduce the Problem

1. Open the GitHub repository on the address: https://github.com/Shopify/polaris
2. Look at the information displayed on the top right corner of the info bar.
3. Look at the package.json file, and see what "license": type is there.

Specifications

• Polaris version: v1.0.1
• React version:
• Browser:
• Device:
• Operating System:

Issue summary

Chart Type is blank.

Expected behavior

There is content about it.

Actual behavior

Chart Type is listed on sidenav of polaris.shopify.com/visuals/data-visualizations but there's content.

Steps to Reproduce the Problem

1. Go to polaris.shopify.com/visuals/data-visualizations
2. Select Chart Type on the sidenav
3. Nothing happens

Specifications

• Polaris version:
• React version:
• Browser: Chrome
• Device: Macbook
• Operating System: OSX

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Issue summary

Some components like Badges, or the ResourceList in focused state overlap other elements. Tried to add z-index to the components, but not working at all.

• Polaris version: 1.0.2
• React version: 15.5.4
• Browser: Chrome
• Device: Macbook Pro 2015 Retina
• Operating System: macOS Sierra 10.12.4

Issue summary

Tabs.scss contains a misspelled CSS class for the selected tab rules.

Expected behavior

CSS rules on line 79 and 86 should use Polaris-Tabs__Tab--selected to apply the active state border to the active item.

Actual behavior

CSS rules on line 79 and 86 are using Polaris-Tabs__Tab-selected which uses a single hyphen instead of a double when extending the class.

Steps to Reproduce the Problem

Try to set the active tab when using the tab component inside of any view.

Hi,

The type scale 'micro' is mentioned under https://polaris.shopify.com/visuals/typography#emphasis-styles, but that doesn't seem to be on the type scale. I assume this was defined in a previous version and left in accidentally

Issue summary

The <input type="text" /> element the TextField component renders are unable to be typed in.

Expected behavior

The <input type="text" /> element the TextField component renders should be able to be typed in.

Actual behavior

All keypresses get ignored.

Steps to Reproduce the Problem

1. Go here
2. Scroll to the demo section and try and type in the text box
3. Nothing happens

Specifications

• Polaris version: 1.0.2
• React version: 15.5.4
• Browser: Chrome
• Device: Macbook Pro
• Operating System: macOS Sierra

Issue summary

'DisplaySmall' is the only locked layer on the 'Titles and text' artboard on the 'Components' page of the UI Kit.

Expected behavior

Should be unlocked like the rest of the typescale.

Actual behavior

N/A

Steps to Reproduce the Problem

1. Open UI Kit sketch file
2. Click components page
3. Navigate to Titles and text artboard for mobile and desktop
4. Try select 'DisplaySmall' - it's locked.

Specifications

• Polaris version: 1.0.0

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Issue summary

The color picker example is broken. The page loads but on interaction with the components, JS errors occur and the component does not work.

https://polaris.shopify.com/components/forms/color-picker#navigation

Expected behavior

The color picker component should allow you to alter the options for color hue and transparency

Actual behavior

The color does not change in the picker and in the JS console, the following error occurs.

Steps to Reproduce the Problem

1. Visit the Color picker example page
2. Click on any of the elements (square gradient, vertical color bar, vertical transparency bar)
3. No visible UI changes
4. Errors are shown in the developer tools console

Specifications

• Polaris version: N/A
• React version: N/A
• Browser: Chrome 57
• Device: Macbook Pro
• Operating System: OSX 10.12.3

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Issue summary

Clicking on ResourceList.Item doesn't change the URL.

Expected behavior

Clicking on ResourceList.Item should go to the url prop

Actual behavior

Nothing

Specifications

• Polaris version: 1.0.1
• React version: 15.4.2

This is where it is in the code:
https://github.com/Shopify/polaris/blob/master/src/components/ResourceList/Item.tsx#L188-L193

Looks like containerMarkup needs to be added as a child of UnstyledLink

Issue summary

When I´m testing the example "polaris/examples/webpack/" show me the error: "Module build failed: Error: Couldn't find preset "shopify/node" relative to directory"

Actual behavior

Inside polaris/examples/webpack, after yarn install and yarn start show me an error: "Module build failed: Error: Couldn't find preset "shopify/node" relative to directory ..."

Steps to Reproduce the Problem

1. Inside polaris/examples/webpack;
2. yarn install;
3. yarn start.

Specifications

• Polaris version: 1.0.0
• React version: 15.4.2
• Browser: Chrome
• Device: PC
• Operating System: Windows 10

Issue summary

Steps to Reproduce the Problem

1. Go to https://polaris.shopify.com/components/tables-and-lists/description-list
2. In the example section, click "HTML"

Expected behavior

<dl class="Polaris-DescriptionList"><dt class="Polaris-DescriptionList__Term">Logistics</dt>
  <dd class="Polaris-DescriptionList__Description">The management of products or other resources as they travel between a point of origin and a destination.</dd><dt class="Polaris-DescriptionList__Term">Sole proprietorship</dt>
  <dd class="Polaris-DescriptionList__Description">A business structure where a single individual both owns and runs the company.</dd><dt class="Polaris-DescriptionList__Term">Discount code</dt>
  <dd class="Polaris-DescriptionList__Description">A series of numbers and/or letters that an online shopper may enter at checkout to get a discount or special offer.</dd>
</dl>

Note that navigating away to another component, and then back to the Description List component shows this expected code.

Actual behavior

<pre class="error">There is an error in your code.</pre>

Specifications

• Polaris version: latest documentation
• Browser: Chrome
• Operating System: macOS

Issue summary

In the Color Palette in the documentation, "Title Bar" does not have a Sass representation.

Should it?

https://polaris.shopify.com/visuals/colors

Issue summary

Cannot select options in choice-list

Expected behavior

Options become selected

Actual behavior

Options are not selected

Steps to Reproduce the Problem

1. Visit https://polaris.shopify.com/components/forms/choice-list#navigation
2. Click an option in the example
3. Option is not selected

Steps to reproduce:

1. Go to: https://polaris.shopify.com/components/structure/layout#navigation
2. Set sectioned to false, then true
3. Observe below styling issue:

Issue summary

The select component always sets the option value to the option text. There is no way to define options with text and values that differ.

Expected behavior

The select component should have a way to set options that differ in value and display text. Possibly accepting a JSON structure would work.

options={[
	{"text": "red", "value": "1"},
	{"text": "white", "value": "2"},
	{"text": "blue", "value": "3"}]}

<select id="tester" name="tester" class="Polaris-Select__Input" aria-invalid="false">
	<option value="1">red</option>
	<option value="2">white</option>
	<option value="3">blue</option>
</select>

Actual behavior

The select component only accepts an array of option values

options={['red', 'white', 'blue']}

The select component always sets the option text to the option value

<select id="tester" name="tester" class="Polaris-Select__Input" aria-invalid="false">
	<option value="red">red</option>
	<option value="white">white</option>
	<option value="blue">blue</option>
</select>

Steps to Reproduce the Problem

<Select value=""
	name="tester"
	options={['red', 'white', 'blue']}
/>

Specifications

• Polaris version: v1.0.2
• React version: 15.5.4
• Browser: Chrome 57
• Device: MacBook Pro
• Operating System: 10.12.4

I have one question, but before that let me thank the team behind this awesome project, it is really a piece of art and should get more stars here in Github.

For my question I wonder if there is a place where I can clone the documentation around visuals(colors, typography, etc) for offline browsing something like a gh-pages or similar.

Thanks for your time.

It would be great if <Page> component can support all the attributes that ShopifyApp.Bar.initialize supports in the embedded app SDK.

Something like:
<Page secondaryActions={[{content: 'About', url: '/about', target: 'app'}]}>

Or
<Page secondaryActions={[{content: 'About', onClick: () => history.push('/about')}]}>

Issue summary

It is unclear whether embedded apps will continue to use the SDKs ShopifyApp.Bar from the javascript API (and it's breadcrumbs and primary/secondary buttons), or whether the app bar will disappear in the new version in favor of the new Polaris page header navigation style (without the app bar).

Will the app bar be disappearing with the release of Polaris? Or will javascript instantiated components (breadcrumbs, titles, etc.) be rendered with Polaris style when using the javascript API going forward?

Expected behavior

The javascript initialized app bar gets styled to match Polaris page header styling.

Actual behavior

It is unclear whether a CSS only embedded app should use the ShopifyApp.Bar or should use html/CSS for the Polaris Page Header Elements and not use the ShopifyApp.Bar.

Steps to Reproduce the Problem

1. Have a CSS only embedded app
2. Use the Shopify embedded app SDK
3. Wonder what page header navigation system you are supposed to use.

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Issue summary

It is not entirely clear the colored circles in the Color Usage section of the docs are clickable.

Expected behavior

Perhaps the circles should change color or a more obvious "link" is used.

Issue summary

While the Shopify Polaris color theme is great, how do we go about creating a customized color theme without losing the ability to merge in updates into our codebase and / sketch file?
A bigger question is, does Polaris encourage changing the color theme based on branding, or are we, as developers/designers on our own if we do choose to change colors to match?

Expected behavior

The Sketch Web.UIKit.sketch file should have used shared styles to make colors customizable so that app developers can customize the colors to fit branding while keeping the structure in place. This is possible in the CSS, however it is not in the Sketch file.

Actual behavior

Sketch Web.UIKit.sketch hard codes colors into every symbol, thus it is hard to start using if we wanted customized branding.

Specifications

N/A

Issue summary

After downloading the UI kit, when opening it I'm presented with a missing fonts dialog but am not given the fonts necessary to reconcile the issue.

Expected behavior

I should be presented ahead of time with font requirements and download locations.

Actual behavior

I'm presented with an error dialog, and the natural next step is to go looking for the fonts, not dismiss it and open the file anyway, which is the only way to see the link to get the necessary fonts.

Issue summary

Sketch UI kit sometimes uses Graphik Regular font rather than SFUI, causing missing font error for those without the font installed.

Expected behavior

SFUI font installation should resolve all missing font issues.

Actual behavior

Graphik regular used inconsistently in some places where SFUI appears to be preferred.

Steps to Reproduce the Problem

1. Disable Graphik Regular font if installed.
2. Open Sketch UI kit

To correct

1. Install Font Finder sketch plugin
2. Run plugin on "Examples - Core" page of Sketch file
3. Replace incorrect font

Expected behavior

EmbeddedApp component with forceRedirect: true should redirect the app to the relative admin path when not rendered in an iframe

Actual behavior

I've inspected the code and it seems that it only sends the message but never actually redirects.
https://github.com/Shopify/polaris/blob/master/src/embedded/easdk/EASDK.ts#L58

I initialize the component like this

<EmbeddedApp
   shopOrigin={shopOrigin}
   apiKey={apiKey}
   forceRedirect>
   {children}
</EmbeddedApp>

Issue summary

ColorPicker README shows wrong maximum values for saturation and brightness.
https://github.com/Shopify/polaris/tree/master/src/components/ColorPicker

Expected behavior

The maximum values for saturation and brightness should be shown 1 as in practice the callback function receives a value between 0 and 1 for these values.

Actual behavior

They are being shown as 255 for a maximum value.

Specifications

• Polaris version: N/A
• React version: N/A
• Browser: N/A
• Device: N/A
• Operating System: N/A

https://polaris.shopify.com/visuals/colors does not render for me:

Issue summary

On the Web.UIKit.sketch the typestyle 02 Subheading is using semibold but the weight reads bold.

Specifications

• Polaris version: v1.0.2

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Issue summary

An error is thrown if you do not define the onClose prop for the Popover component.

Expected behavior

No error should be thrown, or the documentation should include a "required" properties column.
None of the examples used the onClose prop, that's why it was an unexpected error. In actual usage I imagine most people will be defining onClose.

Actual behavior

The error happens when clicking on the invisible PopoverOverlay element.

TypeError: this.props.onClose is not a function
at Popover.handleClose
at PopoverOverlay.handleClick

The problem is here:
https://github.com/Shopify/polaris/blob/master/src/components/Popover/Popover.tsx#L101

handleClose gets called when PopoverOverlay closes and it's always assuming this.props.onClose is defined.

Steps to Reproduce the Problem

1. A Popover must be open
2. Click anywhere outside of the Popover (this click is registered on the PopoverOverlay element)
3. Error is thrown (unless you defined the onClose prop)

Specifications

• Polaris version: 1.0.2
• React version: 15.5.0

Issue summary

See below. I would’ve submitted a PR, but 1) you’re not accepting those yet and 2) I couldn’t find the source of the text to edit.

Expected behavior

In the ‘Do’ column, based on the code sample below it, it seems like it should say:

Use any light background color with its corresponding dark color for an action

Actual behavior

It currently says:

Use any light background color with its corresponding primary color for an action

Steps to Reproduce the Problem

1. https://polaris.shopify.com/visuals/colors#color-combinations
2. Scroll down a bit

Issue summary

The link within the smaller text blurb:

This component only works within embedded apps. Read the EASDK getting started guide for more details on how to use the EASDK with Polaris.

refers to the wrong location.

Expected behavior

The link should probably refer to the same link as the larger text above https://help.shopify.com/api/sdks/shopify-apps/embedded-app-sdk/getting-started

Actual behavior

Navigates you to https://github.com/Shopify/polaris/blob/master/documentation/Embedded%20apps.md

Steps to Reproduce the Problem

1. Click the link
2. Get to a 404 page on github

Specifications

• Polaris version: N/A
• React version: N/A
• Browser: All
• Device: All
• Operating System: All

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Issue summary

When navigating to the page https://polaris.shopify.com/components/navigation/link (either through the link on the pagination page or by going directly to it) the page content doesn't load.

Expected behavior

It should load the documentation.

Actual behavior

It doesn't load the documentation, it remains stuck in the loading state.

Steps to Reproduce the Problem

1. Navigate to the page https://polaris.shopify.com/components/navigation/link

Specifications

• Polaris version: 1.0.2
• React version: I don't know. 15 something something
• Browser: Chrome 57.0.2987.133 (64-bit)
• Device: Macbook Pro
• Operating System: MacOS

Issue summary

Would like the ability to be able to optionally pass previously selected products/collections when using the Resource Picker.

Expected behavior

Passing the products/collections will show them as already selected in the list when reopening the Resource Picker.

Specifications

• Polaris version: 1.0.2

Sorry that this issue isn't directly related to this codebase, but I'm really impressed with the style guide and I'm curious how you guys are building that.

Issue summary

Would like a file form element component

Expected behavior

Be able to add a file upload field to a form using a Polaris React component

Actual behavior

There's nothing in the documentation at https://polaris.shopify.com/components/ to explain how to add a file upload field to a form using Polaris components.

Issue summary

Tables are missing from "Tables and Lists" section of the component documentation - https://polaris.shopify.com/components/get-started

Expected behavior

Tables are a critical UI component of Shopify. The name "Tables and Lists" implies tables would be included.

Actual behavior

Table examples are missing from documentation.

–Not an issue, just a question.–

On typography, why using px instead of using em?

It's obvious that as a designer we have more control of everything using px, but using em or rem we put the user first, assuming his preferences and limitations.

A person with visibility limitations can set his default font size as Big on browser settings, but he won't see any difference in a site using px.

I am not saying that px is bad, ugly and smell, just trying to understand the choice.

Issue summary

Example input field does not preserve input value

Expected behavior

If I type in "Dog", it should say Dog, not g (since only last input is preserved.)

Actual behavior

I type in "Dog", and only g is displayed.

Steps to Reproduce the Problem

1. Go to: https://polaris.shopify.com/components/titles-and-text/display-text#examples (Or any exmple with an input field)
2. Type in "Dog"
3. Observe only g is displayed.

Specifications

• Polaris version: 1.0.1

Issue summary

@shopify/images is not found when using Typescript

Actual behavior

Specifications

• Polaris version: 1.0.2
• React version: 15.4.2

Hi !

We often need (especially in modal that lead to a deletion or for long running tasks) to have a button with a spinner. This is currently the case for instance in the admin when importing large number of products.

Of course there is the app bar feature, but it's often a better experience, especially on delete, to simply show a spinner on the button when clicking on it instead of immediately closing the modal, as some unexpected error could happen during the deletion.

In the button component, adding a "loading" or "spinning" property would be an awesome addition ;).

If you need further details about use cases, do not hesitate to ask me :).

Issue summary

The Polaris-ResourceList__Item--persistActions class suggested in the docs for the ResourceList component does not match the CSS class in the styles.scss file that's generated.

Expected behavior

CSS should use Polaris-ResourceList__Item--persistActions

Actual behavior

CSS is using Polaris-ResourceList__Item-persistActions.

Steps to Reproduce the Problem

Try to implement a ResourceList item with actions and it will not show the actions since the CSS to unhide the element never gets applied.

Specifications

• Polaris version: 1.0.0

Issue summary

Display Metrics is listed twice.

Expected behavior

One should be removed.

Actual behavior

Display Metrics is listed twice on the sidenav and in the content on polaris.shopify.com/visuals/data-visualizations

Steps to Reproduce the Problem

1. Go to polaris.shopify.com/visuals/data-visualizations
2. Look at the nav

Specifications

• Polaris version:
• React version:
• Browser: Chrome
• Device: Macbook
• Operating System: OSX

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Hi Shopify team,
Do you know if there will be a VueJs support in the future?

Issue summary

Previously I've been initializing my embedded app using

ShopifyApp.init({
  apiKey: 'YOUR_APP_API_KEY',
  shopOrigin: 'https://CURRENT_LOGGED_IN_SHOP.myshopify.com'
});

as described on https://help.shopify.com/api/sdks/shopify-apps/embedded-app-sdk/initialization

If the page is opened outside of the Shopify admin then this causes the Shopify admin to load showing my page inside it.

From the documentation I believe that when I'm using Polaris I don't need to call ShopifyApp.init() as <EmbeddedApp></EmbeddedApp> is supposed to handle this for me. For example:

<EmbeddedApp shopOrigin={shopOrigin} apiKey={apiKey} >
    <ResourcePicker
      open
      products
      onSelection={(resources) => console.log('Selected resources ', resources)}
    />
</EmbeddedApp>

This appears to be attempting to initialize Shopify by posting a message:

"Posting message: {"message":"Shopify.API.initialize","data":{"apiKey":"xxxxxxxxxxxxx","shopOrigin":"https://growing-ecommerce.myshopify.com","metadata":{"@shopify/polaris":"1.0.2"}}} to https://growing-ecommerce.myshopify.com }"

That fails if the page isn't already loaded inside the Shopify Admin with

Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://growing-ecommerce.myshopify.com’) does not match the recipient window’s origin (‘https://localhost:5000’).

Expected behavior

If I open a page with <EmbeddedApp></EmbeddedApp> on it outside of the Shopify Admin then I expect it to load the Shopify Admin with my page inside it.

This is needed to get back into the Shopify Admin after logging in. For example:

1. User goes to the login page https://my-app/login?shop=example.myshopify.com
2. User is redirected to Shopify OAuth page via a full page redirect so they are no longer inside the Shopify Admin (see https://help.shopify.com/api/sdks/shopify-apps/embedded-app-sdk/getting-started)
3. After successful authentication they are redirected back to our app (still outside of the Shopify admin) where they are logged in and redirected to the apps home page
4. The user now sees the app's home page which contains <EmbeddedApp></EmbeddedApp> but they remain outside of the Shopify admin because the initialize isn't working. (See "Steps to Reproduce the Problem" for how I'm currently working around this)

Actual behavior

My page loads without loading the Shopify Admin

Steps to Reproduce the Problem

1. Create a page with <EmbeddedApp shopOrigin={shopOrigin} apiKey={apiKey} ></EmbeddedApp> on it.
2. Visit that page outside of the Shopify Admin.
3. Instead of redirecting you so the page appears as an embedded app inside the Shopify Admin you should see your page outside of the Shopify Admin.
4. Add ShopifyApp.init({apiKey: apiKey, shopOrigin: shopOrigin }); so that it's called before the <EmbeddedApp></EmbeddedApp>
5. Visit the page outside of the Shopify Admin.
6. It should now redirect so the page is loaded as an embedded app inside the Shopify Admin. <-- I'm using this approach to get around it.

Specifications

• Polaris version: 1.0.2
• React version: 15.5.4
• Browser: Firefox 53.0
• Device: Mac
• Operating System: 10.12.4

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Issue summary

Missing NPM dependency when developing in TypeScript.

Expected behavior

After installing Polaris using

npm install @shopify/polaris --save

I expect to be able to compile applications using the TypeScript compiler.

Actual behavior

When running tsc the following error is produced:

Steps to Reproduce the Problem

1. Create a new React app using TypeScript. Verify that it compiles ok
2. Install Polaris using npm install @shopify/polaris --save
3. Add some code that uses Polaris (I have a sample at https://github.com/buggy/polaris-demo)
4. Attempt to compile the application using tsc. You'll now see the error.

This can be fixed by running npm install @shopify/images --save to add the missing dependency.

Specifications

• Polaris version: 1.0.1
• React version: 15.5.4
• Browser: Firefox 53.0
• Device: Mac
• Operating System: 10.12.4

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

Issue summary

The symbol should be rotated 90°.

Expected behavior

The No symbol or prohibition sign has a diagonal line running from top left to bottom right.

https://en.wikipedia.org/wiki/No_symbol

Actual behavior

The symbols in Web.UIKit.sketch Components page on the 🖥 Feedback indicators - Banners
and 📱 Feedback indicators - Banners artboards have diagonal lines running from top right to bottom left.

Issue summary

The TypeScript compiler is unable to find the type definition for @shopify/polaris/embedded at the following line:

import {EmbeddedApp} from "@shopify/polaris/embedded";

Expected behavior

I expect it to be able to find the type definition for @shopify/polaris/embedded and import the EmbeddedApp component .

Actual behavior

When running tsc I receive the following error:

Steps to Reproduce the Problem

I took the embedded app example from https://github.com/Shopify/polaris/blob/master/documentation/Embeddded%20apps.md and modified it to work with TypeScript. The new code is:

import * as React from "react";
import {Page, Card} from "@shopify/polaris";
import {EmbeddedApp} from "@shopify/polaris/embedded";

export default class MyApp extends React.Component<undefined, undefined> {
  render() {
    return (
      <EmbeddedApp
        apiKey="YOUR_APP_API_KEY"
        shopOrigin="https://CURRENT_LOGGED_IN_SHOP.myshopify.com"
      >
        <Page title="Example application">
          <Card sectioned>
            Insert the rest of your app here, including those components detailed below, which can now communicate with the Embedded App SDK.
          </Card>
        </Page>
      </EmbeddedApp>
    );
  }
}

The TypeScript compiler reports that it cannot find @shopify/polaris/embedded/

If I append export * from './embedded'; at the bottom of polaris/types/index.d.ts then import {EmbeddedApp} from "@shopify/polaris"; it finds the type definition so the file clearly exists and is valid. I'm not sure why TypeScript can't find it.

Specifications

• Polaris version: 1.0.1
• React version: 15.5.4
• Browser: Firefox 53.0
• Device: Mac
• Operating System: 10.12.4
• TypeScript 2.2.2

NOTE: This repo is only used for reporting issues and new feature requests. We are not accepting pull requests at this point in time.

The "Examples - Apps & Channels" page in the provided Sketch file (WebUIkit.sketch) doesn't show any examples of Apps: https://cl.ly/0B3u0z0G3K3J.