Comments (19)
This makes sense to me. As I have been following things lately I have noticed this is the central tension in the project so I am glad to see there is a way everyone can get what they need/want out of it.
from standard.
I'm 👍 on this, thanks for suggesting 🙏 There are some practicalities to it I guess, so lets sync up on those so that we are all on the same page as to what this would entail.
This is what I'm personally thinking of, from the top of my mind:
eslint-config-standard-with-typescript
, both npm module and repository, will be transferred to the new organization and use existing names as the new org see fitts-standard
, both npm module and repository, will be given the same treatment (else deprecated as per standard/ts-standard#291)- Currently the VSCode support is given through (
standard/vscode-standard
)[https://github.com/standard/vscode-standard], if the new organization takes onts-standard
, then maybe it wants to have its own copy ofstandard/vscode-standard
as well? To remove dependency onstandard/vscode-standard
. If so, then such a transition should be assisted with bystandard/vscode-standard
I think (Thoughts @LinusU, @theoludwig?)
Any other practicalities I'm missing? Any other modules or npm-packages that would need to be moved?
Also: Would the new org still rely on eslint-config-standard
or become a self-contained module which copies the current rules over but after that keeps its own maintenance of those? (I think personally this would give the most freedom to the new org)
from standard.
I'm ok with it, +1.
from standard.
@mightyiam Is this still of interest to solve? If so: Reminder @feross. Else we can close this?
from standard.
Also: Would the new org still rely on eslint-config-standard or become a self-contained module which copies the current rules over but after that keeps its own maintenance of those? (I think personally this would give the most freedom to the new org)
The latter.
Otherwise, sounds good.
from standard.
@rostislav-simonik and I would like to implement this RFC (depart eslint-config-standard-with-typescript from @standard). We find it reasonable at this point to announce our intention to implement this RFC after a certain future date: 2024-01-12. DMs will be sent to @feross and @mcollina.
from standard.
The new home is https://github.com/mightyiam/eslint-config-standard-with-typescript .
from standard.
Could someone please make me owner of the eslint-config-standard-with-typescript npm package? @voxpelli perhaps?
from standard.
My npm username is mightyiam.
from standard.
I'm not an admin
/ owner
on npm it seems, ping @LinusU, @bcomnes, @feross
from standard.
Sorry for the delay here. Ok I removed the package eslint-config-standard-with-typescript
from the standardjs developers
team, and mightyiam and rostislav-simonik remain as maintainers.
Does that look right to everyone?
from standard.
@bcomnes thank you. If the 'maintainer' role means full control, then that seems complete. Could you, perhaps do the same for ts-standard?
from standard.
@mightyiam I tried adding you as a maintainer/collaborator on that package on npm but get a forbidden error. As an admin I am unable to invite you back to the org.
from standard.
@feross perhaps you could? @bcomnes could you perhaps ping some who do have permission to do this?
from standard.
@bcomnes Essentially we should do the same thing with ts-standard
as we did with eslint-config-standard-with-typescript
and simply give it over to @mightyiam and remove it form the standard organization – on both npm and on GitHub
from standard.
The difference here's that he's no longer on the package as a collaborator, and I'm unable to add outside collaborators as an admin. I think only owners can do this.
from standard.
@bcomnes a problem on both npm and GitHub or just npm?
from standard.
Npm
from standard.
ts-standard probably belongs together with eslint-config-standard-with-typescript.
I've been making progress there.
So, I would say, yes.
from standard.
Related Issues (20)
- Formatting code will make it unreadable
- Expanding Rostislav and I's contribution, into core
- TS-Standart Changed My Code and Throwing Error
- Create a tutorial to use Standard together with Husky
- Eslint v9 support HOT 2
- Add a lock file HOT 3
- Could you please paste the result of the `npm ls eslint` command? HOT 1
- Remove the lock-threads workflow
- Comments bring issues/PRs onto the project board HOT 1
- tittle
- space-unary-ops errors on `new Class()` syntax HOT 4
- Maintenance & Governance of standard HOT 52
- Format using a formatter instead of ESLint formatting rules HOT 17
- inline link with @ in Super to have link inline or below not above HOT 1
- Tags isn't exported with Export .md or HTML HOT 1
- Ctrl+Shift+E to open/close tag page isn't working HOT 2
- `standard.lintFiles()` doesn't use `process.cwd()` HOT 5
- Rule suggestion: no-constant-binary-expression
- Linting in precommit hooks says File not found
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from standard.