Skip to content
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 example to integrate ESLint import plugin #5

Open
LostCrew opened this issue Jan 11, 2018 · 2 comments
Open

Add example to integrate ESLint import plugin #5

LostCrew opened this issue Jan 11, 2018 · 2 comments

Comments

@LostCrew
Copy link

LostCrew commented Jan 11, 2018

ESLint import plugin is very commonly used in medium/big size projects. Aliases should be configured so that cesium/* maps to node_modules/cesium/Source/* (as it's done for the Webpack config) and the import plugin ceases to return errors.
Are contributions accepted?

@ggetz
Copy link
Contributor

ggetz commented Jan 11, 2018

Hi @LostCrew, yes contributions are welcome! We would ask you add a section to README.md rather than the config file itself, as the goal is to leave the config file as minimal as possible.

@tkazik
Copy link

tkazik commented Mar 17, 2020

Thanks to @LostCrew 's comment, I was able to get IntelliSense working with webpack. The config looks like this:

intellisense

Hope this helps someone in the future...thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants