Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
@fireproof/partykit
Advanced tools
[Fireproof](https://use-fireproof.com) is an embedded JavaScript document database that runs in the browser (or anywhere with JavaScript) and **[connects to any cloud](https://www.npmjs.com/package/@fireproof/connect)**.
@fireproof/partykit
Fireproof is an embedded JavaScript document database that runs in the browser (or anywhere with JavaScript) and connects to any cloud.
🎈 PartyKit is a realtime connection library that's the perfect complement to Fireproof's verifiable sync.
We assume you already have an app that uses Fireproof in the browser, and you want to setup collaboration among multiple users via the cloud or peer-to-peer. To write your first Fireproof app, see the Fireproof quickstart, othwerwise read on. It's also easy to add Fireproof to PartyKit apps, check out this demo repo for live magnetic poetry with database persistence.
PartyKit uses websockets and CloudFlare workers to manage a real-time group. Adding Fireproof requires one-line of config, and it syncs in its own party so you can use it with your existing PartyKit apps without impacting existing code.
In your existing Fireproof app install the connector:
npm install @fireproof/partykit
If you already have PartyKit configured in your project, all you need to do is add one line to the config defining a fireproof
party.:
{
"name": "my-app-name",
"main": "src/partykit/server.ts",
"parties": {
"fireproof": "node_modules/@fireproof/partykit/src/server.ts"
}
}
If you haven't added PartyKit to your app, you want to run the PartyKit CLI to set up the basics:
npx partykit init
Refer to the PartyKit docs for more info on configuring PartyKit.
You're all done on the server, and ready to develop locally and then deploy with no further changes. Now you just need to connect to the party in your client code:
// you already have this in your app
import { useFireproof } from 'use-fireproof'
// add this line
import { connect } from '@fireproof/partykit'
Now later in your app connect to the party (be sure to do this a component that runs on every render, like your root component or layout):
const { database } = useFireproof('my-app-database-name')
const connection = connect.partykit(database, process.env.NEXT_PUBLIC_PARTYKIT_HOST!)
The connect.partykit
function is idempotent, and designed to be safe to call on every render. It takes two arguments, the current database, and the host of your PartyKit server. This will be the same host you are using in your app when calling usePartySocket
and other PartyKit APIs, so once you have it set, you won't need to think about it again.
Now you can use Fireproof as you normally would, and it will sync in realtime with other users. Any existing apps you have that use the live query or subscription APIs will automatically render multi-user updates.
FAQs
PartyKit gateway for Fireproof
The npm package @fireproof/partykit receives a total of 121 weekly downloads. As such, @fireproof/partykit popularity was classified as not popular.
We found that @fireproof/partykit demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.