[GH-ISSUE #68] Linting Tools section of README.md #55

New issue

Open

opened 2026-05-05 15:00:28 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 15:00:28 -06:00

Owner

Originally created by @DaveSprague on GitHub (Sep 5, 2015).
Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/68

I'm just starting to try Meteor and I'm using Atom as my editor/IDE with meteor-api. I've just installed Meteor and Atom on a fresh Mac OS install in the last few days and added the list of recommended Atom packages from the "Setting Up Atom As an Integrated Development Environment" section of the README.md file.

When I open any *.js file I get a bunch of errors found, I believe, by the linting tools. The errors are: ' "Meteor" is not defined.' and ' "Session" is not defined.'

Also up at the top I get a bit red error box that says "[Linter-ESLint] eslint binary not found locally, falling back to packaged one. Plugins won't be loaded and linting will possibly not work. (Try Use Global ESLint option, or install locally eslint to your project.)"

Under the Linting Tools section of the README.md file, it suggests using the command "npm install -g eslint" to install eslint but I don't have a separate Node.js installation aside form whatever comes embedded in the Meteor package and so, as far as I know, I don't have npm.

Is there a way to set up the linter tools to work properly without a separate Node install or, if not, is there a recommended way of installing Node with global npm packages to work with a Meteor/Atom IDE setup?

Thanks,
Dave

Originally created by @DaveSprague on GitHub (Sep 5, 2015). Original GitHub issue: https://github.com/awatson1978/meteor-api/issues/68 I'm just starting to try Meteor and I'm using Atom as my editor/IDE with meteor-api. I've just installed Meteor and Atom on a fresh Mac OS install in the last few days and added the list of recommended Atom packages from the "Setting Up Atom As an Integrated Development Environment" section of the README.md file. When I open any *.js file I get a bunch of errors found, I believe, by the linting tools. The errors are: ' "Meteor" is not defined.' and ' "Session" is not defined.' Also up at the top I get a bit red error box that says "[Linter-ESLint] eslint binary not found locally, falling back to packaged one. Plugins won't be loaded and linting will possibly not work. (Try Use Global ESLint option, or install locally eslint to your project.)" Under the Linting Tools section of the README.md file, it suggests using the command "npm install -g eslint" to install eslint but I don't have a separate Node.js installation aside form whatever comes embedded in the Meteor package and so, as far as I know, I don't have npm. Is there a way to set up the linter tools to work properly without a separate Node install or, if not, is there a recommended way of installing Node with global npm packages to work with a Meteor/Atom IDE setup? Thanks, Dave

gitea-mirror commented

2026-05-05 15:00:30 -06:00

Author

Owner

@DaveSprague commented on GitHub (Sep 7, 2015):

I did find that if I included the .eslintrc file into each project that I no longer get the "Meteor" is not defined type errors. Now the only issue is the "eslint binary not found locally..." error. Any suggestions for getting rid of that? Thanks

@DaveSprague commented on GitHub (Sep 7, 2015): I did find that if I included the .eslintrc file into each project that I no longer get the "Meteor" is not defined type errors. Now the only issue is the "eslint binary not found locally..." error. Any suggestions for getting rid of that? Thanks