
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Ship products faster by adding jam to any project!
Get started by visiting jam.dev.
npm install --save letsjam
import React from "react"
import Jam from "letsjam"
const App = () => {
return <Jam JAM_ID="YOUR_JAM_ID" />
}
First you will run npm install && npm start in the root directory...
cd letsjam
rm -rf node_modules/
npm install
npm start
Then in a new tab in the terminal, you will cd into the example folder which contains a janky little test website (all of the images and things in the site are broken -- it's not you, it's us) and npm intall && npm start there. That will let you preview the npm library on the example site.
cd example
rm -rf node_modules
npm install
npm start
Once you are running the example site, you will want to light up jam and try jamming. To do that, type jam into the example site (it's like a secret password to light up jam, there's no form field, you just type it blankly into the site) you'll enter in your email address and off you go!
It's also great to try the dev local version of the letsjam library on other react apps you happen to have installed and running on your computer. How you do that is:
Make sure letsjam is running by using npm start inside the letsjam directory. This will make sure that any changes you make inside letsjam gets compiled automatically to dist.
Go to your other react or nextjs project directory and do npm install absolute/path/for/letsjam/directory (or yarn add)
To verify that your project correctly installed the latest letsjam module your package.json letsjam line will look like: "letsjam": "file:../letsjam"
If you see any errors at all, just rm- rf node_modules, rm package-lock.json and try again :)
GNU AGPLv3 © Strawberry-Jam-Manufacturers
FAQs
Ship products faster by adding jam to any project!
The npm package letsjam receives a total of 0 weekly downloads. As such, letsjam popularity was classified as not popular.
We found that letsjam demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.