-
Notifications
You must be signed in to change notification settings - Fork 213
A created project comes with linting issues #608
Comments
Hmm, this is another thing I don't replicate. I wonder if you have some global install of eslint or something that is conflicting with Neutrino. Here is the output of me running the same command:
|
I've probably installed dependencies on my early days by mistake [1].
[1]
[2]
[3]
[4]
|
We added a yarn create @neutrinojs/project ci-metrics --debug |
I can't use yarn as per the other issue filed. How can I know that debug flag worked? I don't see anything different. |
I'm not sure if
If it works, you should see the full stdout from the installation of deps, devDeps, and running the one-time lint. Also, looking at your log, it appears that this does in fact run the lint and it wasn't skipped, as previous postulated in spectrum:
https://spectrum.chat/?t=339e83d6-7c69-4c86-883f-de77e709e802 |
No changes.
|
@armenzg I had the same issue...running |
I can reproduce this (Windows 10, node 8.9.4, npm 5.6.0, npx 9.7.1):
|
So this is because the monorepo's |
I've opened #754 to allow using |
Hmmm so there are multiple problems here:
@eliperelman thoughts about the prettier issue? Could we just stop using it? Or else override it to more closely match airbnb? The only other options I could think of were:
|
I want to address the issue here, before I give an answer to your other questions. We don't want to lint create-project templated files the same way as the monorepo. A user can use standardjs, airbnb, or no linting with create-project. One uses semicolons, the other doesn't. Therefore, it's impossible to fix linting issues in the repo prior to them landing in the project: we always have to run a lint fix in the project before handing it off to the user to resolve these types of discrepancies in linting preferences. We have to make sure that whatever we land in the repo is auto-fixable by any of the projects we support out of the box. This means the root of this issue lies in a failing or non-running linting command during the create-project process. This is what needs to be debugged.
|
Oh create-app already tries to perform a one-off lint haha I missed that. |
Ah seeing #714 I think I know what the problem is. The one time lint command is run as @eliperelman presumably this worked locally for you since |
This should be fixed in v8.2.3 - could someone confirm? (I don't currently have npm/npx installed, and currently have the monorepo yarn linked globally, which hides the original issue here anyway) |
This works. Thanks for fixing it! I run the following commands:
My versions:
|
I chose to create a React project with no testing and with the airbnb configuration (created with
npx @neutrinojs/create-project ci-metrics
.After that I would run
yarn start
and I get linting errors.The text was updated successfully, but these errors were encountered: