Npm package namespace for official Meteor config

Question

Npm package namespace for official Meteor config

Closed this issue 8 years ago · 7 comments

Hey @iDoMeteor as part of meteor/meteor#8045 we are looking at creating an official configuration (based on the guide) for use within the newly added scaffold feature. This is something that I am happy to maintain under another repo. Please let me know if that's a possibility, thanks!

Answer 1 · 2016-11-16T05:58:12.000Z

I might be interested in participating. I'll look into the guide recommendations and the scaffold when I get a chance, I'm not really familiar with either atm. You can contact me directly @ Gmail/Hangouts using the same handle.

Answer 2 · 2016-11-16T06:00:33.000Z

Yeah no problem, as I said I'm happy to put it together I'll post a link to the repo once I've made a start

Answer 3 · 2016-11-16T15:04:39.000Z

Have you checked my meteor-skeleton? It's kind of out-dated, but has some
good methodologies. I'm not a big fan of the guide, it pushes too much
towards using add-ons and impractical architecture for most apps.

Answer 4 · 2016-11-19T09:37:17.000Z

Hey @iDoMeteor I've got a configuration underway here with the aim that it will be the official configuration documented within the Meteor guide! It would be great if we could use the eslint-config-meteor namespace on npm, if not I'll have to think of another name, or potentially, it might live under the @mdg namespace.

Answer 5 · 2016-11-19T19:42:12.000Z

I'll consider giving you write access or merging your changes into my repo, have you read my config? Taken any of my rules into consideration?

Answer 6 · 2016-11-19T19:43:22.000Z

MDG tried to get this namespace from me before they adopted the AirBNB.

Answer 7 · 2016-11-19T23:08:05.000Z

I don't see any reason to have to replace your existing repo if that's a concern. I did have a quick look at your configuration.