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

eslint aura conflict in new project #511

Open
SheetJSDev opened this issue Jun 26, 2022 · 6 comments
Open

eslint aura conflict in new project #511

SheetJSDev opened this issue Jun 26, 2022 · 6 comments
Labels
bug Something isn't working

Comments

@SheetJSDev
Copy link

Summary

You are linting "**/aura/**", but all of the files matching the glob pattern "**/aura/**" are ignored.

Steps To Reproduce:

Affects a fresh project using latest sfdx-cli:

$ npx sfdx-cli force:project:create --projectname eslint-issue
$ cd issue
$ npm i
$ npm run lint

Expected result

No error

Actual result

> eslint **/{aura,lwc}/**


Oops! Something went wrong! :(

ESLint: 8.18.0

You are linting "**/aura/**", but all of the files matching the glob pattern "**/aura/**" are ignored.

If you don't want to lint these files, remove the pattern "**/aura/**" from the list of arguments passed to ESLint.

If you do want to lint these files, try the following solutions:

* Check your .eslintignore file, or the eslintIgnore property in package.json, to ensure that the files are not configured to be ignored.
* Explicitly list the files from this glob that you'd like to lint on the command-line, rather than providing a glob as an argument.

System Information

  • Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.) bash

  • If you are using sfdx

    • Run sfdx version --verbose --json
Version (click to show)
$ npx sfdx-cli version --verbose --json
{
	"cliVersion": "sfdx-cli/7.156.1",
	"architecture": "darwin-x64",
	"nodeVersion": "node-v18.4.0",
	"pluginVersions": [
		"@oclif/plugin-autocomplete 0.3.0 (core)",
		"@oclif/plugin-commands 1.3.0 (core)",
		"@oclif/plugin-help 3.3.1 (core)",
		"@oclif/plugin-not-found 1.2.6 (core)",
		"@oclif/plugin-plugins 1.10.11 (core)",
		"@oclif/plugin-update 1.5.0 (core)",
		"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
		"@oclif/plugin-which 1.0.4 (core)",
		"@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
		"alias 2.1.0 (core)",
		"apex 0.13.0 (core)",
		"auth 2.2.0 (core)",
		"community 2.0.0 (core)",
		"config 1.4.12 (core)",
		"custom-metadata 2.0.0 (core)",
		"data 2.0.4 (core)",
		"generator 2.0.1 (core)",
		"info 2.0.1 (core)",
		"limits 2.0.1 (core)",
		"org 1.13.2 (core)",
		"salesforce-alm 54.6.0 (core)",
		"schema 2.1.1 (core)",
		"sfdx-cli 7.156.1 (core)",
		"signups 1.2.0 (core)",
		"source 2.0.2 (core)",
		"telemetry 2.0.0 (core)",
		"templates 55.0.0 (core)",
		"trust 2.0.1 (core)",
		"user 2.1.0 (core)"
	],
	"osVersion": "Darwin 21.2.0"
}

Additional information

The instructions from the official docs (https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.get_started_sfdx_scratch_org) elicit the error in question -- have they been tested?

@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@github-actions
Copy link

This issue has not received a response in 60 days. It will auto-close in 7 days unless a response is posted.

@SheetJSDev
Copy link
Author

Still affects a fresh project using 7.169.1 (tested today) in zsh:

% npx sfdx-cli force:project:create --projectname eslint-issue
% cd eslint-issue
% npm i
% npm run lint

> [email protected] lint
> eslint **/{aura,lwc}/**


Oops! Something went wrong! :(

ESLint: 8.24.0

You are linting "**/aura/**", but all of the files matching the glob pattern "**/aura/**" are ignored.

@cristiand391 cristiand391 added the bug Something isn't working label Sep 26, 2022
@github-actions
Copy link

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

@git2gus
Copy link

git2gus bot commented Sep 26, 2022

This issue has been linked to a new work item: W-11808317

@cristiand391 cristiand391 transferred this issue from forcedotcom/cli Sep 26, 2022
@jefersonchaves
Copy link

Is there any update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants