GithubHelp home page GithubHelp logo

epicweb-dev / config Goto Github PK

View Code? Open in Web Editor NEW
170.0 2.0 7.0 147 KB

Reasonable ESLint, Prettier, and TypeScript configs for epic web devs

Home Page: https://www.epicweb.dev

JavaScript 96.35% TypeScript 3.65%
config eslint-config prettier-config typescript-config epic-web

config's People

Contributors

ironbyte avatar jacobparis avatar kentcdodds avatar philwolstenholme avatar wkovacs64 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

config's Issues

ESLint: package detection strategy

System Info

System:
    OS: Windows 11 10.0.22621
    CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
    Memory: 11.37 GB / 31.92 GB
  Binaries:
    Node: 20.12.2 - ~\AppData\Local\nvs\default\node.EXE
    npm: 10.5.0 - ~\AppData\Local\nvs\default\npm.CMD
  npmPackages:
    @epic-web/config: 1.9.1 => 1.9.1 
    eslint: 8.57.0 => 8.57.0 
    vitest: 1.6.0 => 1.6.0

Expected Behavior

I would expect the ESLint config to find the vitest package installed and conditionally apply the vitest rules.

Actual Behavior

It does not find the vitest dependency and thus does not apply the vitest rules.

Additional Context

Certain packages (e.g., vitest, @playwright/test, etc.) don't like to be imported wholesale like the has function currently does, so dynamic import() rejects and the config doesn't think the package is present.

I solved this in my fork using import.meta.resolve, which I'd be happy to PR if that's the direct you want to go, but thought I'd run it by you here first.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.