The node written before n8n0.209.2 is missing

[Tk8and15]

Describe the issue/error/question

The node I wrote before is missing！

What is the error message (if any)?

Initializing n8n process
n8n ready on 0.0.0.0, port 5678
Version: 0.209.2
» Error: There was an error: SQLITE_ERROR: no such column: WorkflowEntity.dataLoaded

Please share the workflow

(Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively)

Share the output returned by the last node

Information on your n8n setup

• n8n version:
• **Database you’re using (default: SQLite):0.209.2
• **Running n8n with the execution process [own(default), main]:own
• **Running n8n via [Docker, npm, n8n.cloud, desktop app]:npm

[Jon]

Hey @Tk8and15,

Can you double check the node is still installed under the community nodes.

[Tk8and15]

How do I check?

[Tk8and15]

After I update to the latest version, my custom node still does not exist.

[Jon]

Did you install the nodes through the web ui under settings or did you manually do it outside of n8n?

[Tk8and15]

Use the npm install n8n - g command to install

[Tk8and15]

After the link, I can’t understand all kinds of errors. Although n8n can be started, my custom nodes are missing, and I can’t search in the UI page.

[Jon]

Hey @Tk8and15,

Can you try installing the nodes from the ui, that is probably the best way to use them.

[Tk8and15]

What shall I do?
Here is my node directory：

Here is my command:

In the n8n UI, my node is missing. I didn’t know there was a problem. I have done the same before, but my nodes can come out.

[Jon]

The quickest option would be to downgrade n8n to an earlier release.

Another option would be to try publishing your nodes to npm and using the web interface to install them.

[Tk8and15]

How to downgrade n8n to an earlier version?
How to operate the second method?

[Tk8and15]

The version before installation will report a bunch of errors:

[Jon]

What version were you on before you started seeing the issues? Sometimes npm can hit issues when finding packages or looking for OS commands depending on what it is doing.

Did you back up everything before upgrading?

[Tk8and15]

Before the upgrade, 0.209.2 was used. I didn’t have a backup. My code is still in my project directory. I don’t know what you mean by backup.

[Jon]

Try installing the older version again, did the data in the database matter to you or are you just creating nodes?

[Tk8and15]

I’m just creating a node, and then I tried to download the old version, but it didn’t work. I’ll try again.

[Tk8and15]

Sir, this is an error caused by dependency package conflict. The new version can be used without returning to the old version. We just need to add – legacy-peer-deps after our linked project.

[Jon]

That makes sense, it is not the first time we have seen that recently.