javascriptstyled-components/polished #134Not a task: already works

Strange error with eslint

envgap__styled-components__polished-134

Original GitHub issue ↗Dated source checkout ↗Opened 2017-03-30

01 / FAILURE SIGNATURE

As reported upstream

2:32  error  Unable to resolve path to module 'polished'  import/no-unresolved

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 4200341a9ed2c0dd1d132fce6024f636dcd5a695
Manifest: package.json
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

styled-components/polished #134 · read the original issue

I just installed **polished**, and ❤️  it (just like **styled-components**)!



There is just one little bug (?) that bothers me..

I use **eslint** for linting, and it keeps saying me that I have 2 errors for each `import polished from 'polished'`:

```

/polished-test/src/Component.js

  2:32  error  Unable to resolve path to module 'polished'  import/no-unresolved

  2:32  error  Missing file extension for "polished"        import/extensions

```



My guess is that in the npm name there is an invisible character..



Here's how to reproduce it:

```bash

git clone https://github.com/EnoahNetzach/polished-test

cd polished-test

yarn

yarn eslint

```

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]