Registry / database / node-parse-api

node-parse-api

JSON →
library0.3.8jsnpmunverified

This `node-parse-api` library serves as a Node.js client for the Parse.com REST API, offering functionalities like data insertion, user management (login, registration), file uploads, and querying objects. At version 0.3.8, it reflects an early period of Node.js and the Parse.com platform. A critical aspect of this package is its tight coupling to the original Parse.com hosted service, which was officially shut down in January 2017. Consequently, while the package itself is available, its primary utility for connecting to `api.parse.com` is obsolete. There is no indication of active development or a release cadence, and it is likely abandoned, primarily existing as historical reference for developers who might have used the original Parse.com platform. Its design predates modern JavaScript module systems, relying exclusively on CommonJS.

npm install node-parse-api
INSTALL
IMPORT
SIG · NODE-PARSE-API
N
node-parse-api
databasejavascriptv0.3.8
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

Parse
const { Parse } = require('node-parse-api');
import { Parse } from 'node-parse-api';
This package exports a named 'Parse' property from its main module. It is CommonJS only and does not support ES Modules directly.
ParseClient (instance)
const ParseClient = new Parse(APP_ID, MASTER_KEY);
const ParseClient = new require('node-parse-api').Parse(APP_ID, MASTER_KEY);
The 'Parse' constructor should be used after being destructured from the `require` call for cleaner syntax and to avoid re-requiring the module.

Initializes the Parse API client with an App ID and Master Key and demonstrates inserting a new object into a Parse class. Note: This library targets the now-defunct Parse.com service.

const { Parse } = require('node-parse-api'); const APP_ID = process.env.PARSE_APP_ID ?? ''; const MASTER_KEY = process.env.PARSE_MASTER_KEY ?? ''; // Ensure environment variables are set or replace with actual values (not recommended for production) if (!APP_ID || !MASTER_KEY) { console.error('PARSE_APP_ID and PARSE_MASTER_KEY environment variables must be set.'); process.exit(1); } const app = new Parse(APP_ID, MASTER_KEY); // Insert an object into a 'Foo' class app.insert('Foo', { foo: 'bar', timestamp: new Date() }, function (err, response) { if (err) { console.error('Error inserting object:', err); return; } console.log('Successfully inserted object:', response); // A real application would typically have more operations here. // Given Parse.com is shut down, this example is primarily illustrative. });
Debug
Known issues
breakingThe Parse.com hosted service, which this library directly targets (`api.parse.com`), was officially shut down on January 28, 2017. This package is **not functional** for its original purpose of connecting to the cloud-hosted Parse.com backend.
fix
This package is effectively obsolete for its original purpose. Developers should migrate to an alternative Parse Server client (e.g., the official `parse` npm package which targets self-hosted Parse Server instances) or a completely different backend solution.
affects: >=0.0.1
gotchaThis package is not actively maintained. It was last published almost a decade ago and targets very old Node.js runtimes (specified as `>= 0.4.0`). Using it with modern Node.js versions may lead to unexpected behavior, compatibility issues, or security vulnerabilities due to unpatched dependencies.
fix
Avoid using this package in new projects. For historical projects, a full migration to a modern Parse SDK or another backend is strongly recommended.
affects: >=0.0.1
gotchaThe library explicitly uses CommonJS `require()` syntax. It does not natively support ES Modules (`import`) and attempting to use `import { Parse } from 'node-parse-api';` in an ESM-only context will result in a runtime error.
fix
Ensure your project is configured for CommonJS, or use `const { Parse } = require('node-parse-api');` in a context where CommonJS interoperability is supported.
affects: >=0.0.1
Errors
Common errors & fixes
Error: connect ECONNREFUSED
The application is attempting to connect to `api.parse.com` which is no longer active, or a misconfigured self-hosted Parse Server is unreachable.
fix
This library is designed for the defunct Parse.com service. If attempting to connect to a self-hosted Parse Server, this specific library might not be suitable or require internal modifications (e.g., `Parse._api_host`). Consider using the official `@parse/node` or `parse` npm packages instead.
TypeError: app.insert is not a function
The `Parse` object was not correctly instantiated as a client instance, or the imported `Parse` object is not the expected constructor.
fix
Ensure you are instantiating the `Parse` client correctly after requiring it: `const { Parse } = require('node-parse-api'); const app = new Parse(APP_ID, MASTER_KEY);`
Cannot find module 'node-parse-api'
The package has not been installed or is not correctly linked in the project.
fix
Run `npm install node-parse-api` to add the package to your project dependencies.
Upgrade
Version history
0.3.8latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
12 hits · last 30 days
node
10
Amazon
1
OpenAI (training)
1
Resources
node-parse-api — npm install node-parse-api · libregistry