kartik-mem0
a618939f00
The unscoped `n8n-nodes-mem0` name is already taken on npm by an unrelated publisher, so the CD workflow could never publish it. Move to the `@mem0` scope, matching `@mem0/pi-agent-plugin` and `@mem0/openclaw-mem0`, and add `publishConfig.access: public` since scoped packages default to restricted. n8n accepts scoped community packages: it strips the scope before enforcing the `n8n-nodes-` prefix, the same shape as n8n's own `@n8n/n8n-nodes-langchain`. Verified end to end on n8n 2.22.6 by installing the packed tarball into the community-packages directory and executing a workflow against node type `@mem0/n8n-nodes-mem0.mem0`. The directory, workflow filenames, and the `n8n-nodes-mem0-v*` tag prefix are unchanged. pnpm-lock.yaml needs no update: the pnpm v9 root importer is anonymous and never recorded the package name.
Mintlify Starter Kit
Click on Use this template to copy the Mintlify starter kit. The starter kit contains examples including
- Guide pages
- Navigation
- Customizations
- API Reference pages
- Use of popular components
Development
Install the Mintlify CLI to preview the documentation changes locally. To install, use the following command
npm i -g mintlify
Run the following command at the root of your documentation (where mint.json is)
mintlify dev
Publishing Changes
Install our GitHub App to auto-propagate changes from your repo to your deployment. Changes will be deployed to production automatically after pushing to the default branch. Find the link to install on your dashboard.
Troubleshooting
- Mintlify dev isn't running - Run
mintlify installit'll re-install dependencies. - Page loads as a 404 - Make sure you are running in a folder with
mint.json