Skip to content

import/order generates wrong order with 2.0 #34

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

Closed
Evalon opened this issue Oct 17, 2019 · 3 comments
Closed

import/order generates wrong order with 2.0 #34

Evalon opened this issue Oct 17, 2019 · 3 comments

Comments

@Evalon
Copy link

Evalon commented Oct 17, 2019

After upgrade to resolver 2.0 import/order plugin starts generate wrong order for files that locally redefined.
For example: styled-components recommend use declaration merging (https://www.styled-components.com/docs/api#create-a-declarations-file) for use theme in styled.
Before version 2.0 this imports (e.g import styled from 'styled-components') was "external" but now it's "local". This is prevent me to upgrade to version 2.0.

@Evalon Evalon changed the title import/order generate wrong order with 2.0 import/order generates wrong order with 2.0 Oct 17, 2019
@JounQin
Copy link
Collaborator

JounQin commented Oct 17, 2019

You should post issue at eslint-plugin-import instead.

Related: un-ts#14 (comment)

@cryptiklemur
Copy link

How would i change the order so @paths imports show above relative imports?

@JounQin
Copy link
Collaborator

JounQin commented Dec 14, 2019

How would i change the order so @paths imports show above relative imports?

@aequasi Sorry, but I have no idea what's your point. If you got any problem, please raise another issue with a minimal runnable reproduction please.

@import-js import-js locked as resolved and limited conversation to collaborators Dec 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

3 participants