@n8n/scan-community-package failing for cred filename

Questions
, ,
1

Hi folks, unfortunately im not able to pass the auto checks by @n8n/scan-community-package when submit the package on creator portal.

Describe the problem/error/question

The problem with some Lint Rules, its passing on local cause it the file name has correct extension ts. But when i deploy, its checking same lint rule against dist folder. And there is not ts files in dist folder.
If i found the correct codebase here is the problem i think: eslint-plugin-n8n-nodes-base/lib/rules/cred-filename-against-convention.ts at master · ivov/eslint-plugin-n8n-nodes-base · GitHub

What is the error message (if any)?

$ npx @n8n/scan-community-package @ambriel-io/n8n-nodes-ambriel

 1:2  error  Rename file to AmbrielApi.credentials.ts [non-autofixable]  n8n-nodes-base/cred-filename-against-convention

✖ 1 problem (1 error, 0 warnings)

And the class is exported as below. dist/credentials/AmbrielApi.credentials.js

"use strict";
Object.defineProperty(exports, "\__esModule", { value: true });
exports.AmbrielApi = void 0;
class AmbrielApi {
     constructor() {
     this.name = 'ambrielApi';
     this.displayName = 'Ambriel API';
....

Content of dist/credentials/AmbrielApi.credentials.d.ts

import type { IAuthenticateGeneric, Icon, ICredentialTestRequest, ICredentialType, INodeProperties } from 'n8n-workflow';
export declare class AmbrielApi implements ICredentialType {
    name: string;
    displayName: string;
    icon: Icon;
    documentationUrl: string;
    properties: INodeProperties[];
    authenticate: IAuthenticateGeneric;
    test: ICredentialTestRequest;
}

Information on your n8n setup

  • n8n version: 2.31.4
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: macos
2

We have taken a look at this and it looks like it might be fixed in a recent release, Please update and see if you are still running into the same problem.

3

Just to update the above @bencagri can you try running…

npx @n8n/scan-community-package@beta @ambriel-io/n8n-nodes-ambriel

There was an issue with the tagged release which will be resolved in the morning, using beta will be the best option and will run the latest lints and checks.

4

Hello Jon, thanks for the update.

Indeed, @beta tag worked on my local. Then Im waiting for the update to resubmit on creator portal.

Best.
C

5

You can submit on the portal it should be using the beta version there as well.