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/update eslint plugin dependencies across repo #9976

Merged
merged 5 commits into from
Apr 21, 2022
Merged

Conversation

tylerbutler
Copy link
Member

Adding dependencies pre-emptively because they'll be needed once #9748 is merged and applied.

@tylerbutler tylerbutler requested review from msfluid-bot and a team as code owners April 20, 2022 01:02
@github-actions github-actions bot added area: dds Issues related to distributed data structures area: dds: propertydds area: dds: sharedstring area: definitions area: dev experience Improving the experience of devs building on top of fluid area: driver Driver related issues area: examples Changes that focus on our examples area: framework Framework is a tag for issues involving the developer framework. Eg Aqueduct area: loader Loader related issues area: odsp-driver area: runtime Runtime related issues area: server Server related issues (routerlicious) area: tests Tests to add, test infrastructure improvements, etc dependencies Pull requests that update a dependency file base: main PRs targeted against main branch labels Apr 20, 2022
@heliocliu
Copy link
Contributor

This is gross 😕 Are we not able to pull in the dependencies through the eslint-config-fluid package? Or does that count as a transitive dependency that we need to explicitly specify because of how the tsconfigs from eslint-config-fluid are used?

@tylerbutler
Copy link
Member Author

This is gross 😕 Are we not able to pull in the dependencies through the eslint-config-fluid package? Or does that count as a transitive dependency that we need to explicitly specify because of how the tsconfigs from eslint-config-fluid are used?

I thought so too, but I hit another problem :( It's because of how fluid-build calls eslint, as far as I can tell. The patch is supposed to change how eslint finds plugins, but when it is called from within fluid-build, it doesn't look in the right place. I'd like to fix fluid-build, but then we're also moving to yarn so I think this is the gross but pragmatic choice.

@tylerbutler
Copy link
Member Author

BTW, this is how eslint works by default -- plugins are resolved relative to the local package, not relative to the parent (inherited) config package, and they punted on changing that. So without the rushstack modern-module-resolution patch, everyone using shared configs has this problem. :(

@anthony-murphy
Copy link
Contributor

anthony-murphy commented Apr 20, 2022

BTW, this is how eslint works by default -- plugins are resolved relative to the local package, not relative to the parent (inherited) config package, and they punted on changing that. So without the rushstack modern-module-resolution patch, everyone using shared configs has this problem. :(

i don't know if it is right or wrong, but what i did with type validation only requires tools to be installed at the root. this has the downside of not being able to build packages directly (although it works in most cases, maybe because i global install some things), but keeps our packages light weight and easy to maintain in terms to tooling. we could consider something similar with eslint.

@tylerbutler tylerbutler merged commit 63ba321 into main Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: dds: propertydds area: dds: sharedstring area: dds Issues related to distributed data structures area: definitions area: dev experience Improving the experience of devs building on top of fluid area: driver Driver related issues area: examples Changes that focus on our examples area: framework Framework is a tag for issues involving the developer framework. Eg Aqueduct area: loader Loader related issues area: odsp-driver area: runtime Runtime related issues area: server Server related issues (routerlicious) area: tests Tests to add, test infrastructure improvements, etc base: main PRs targeted against main branch dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants