Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@vercel/toolbar
Advanced tools
Manually inject the Vercel toolbar on any site.
npm install @vercel/toolbar
This library can be used with any framework
import { mountVercelToolbar } from '@vercel/toolbar';
if (userIsEmployee) {
mountVercelToolbar();
}
import { mountVercelToolbar, unmountVercelToolbar } from '@vercel/toolbar';
function VercelToolbar() {
const shouldInjectToolbar = useIsUserEmployee();
useEffect(() => {
if (shouldInjectToolbar) {
// Returns a cleanup function to unmount the toolbar
return mountVercelToolbar();
}
}, [shouldInjectToolbar]);
return null;
}
For usage in Next.js, you can instead import the VercelToolbar
component which will use next/script
:
import { VercelToolbar } from '@vercel/toolbar/next';
export default function MyApp({ Component, pageProps }) {
const shouldInjectToolbar = useIsUserEmployee();
return (
<>
<Component {...pageProps} />
{shouldInjectToolbar && <VercelToolbar />}
</>
);
}
localhost
Allows you to view comments left in your preview deployment while developing locally.
Prerequisites:
vc link
Adjust the code above, to always inject the toolbar in development
import { VercelToolbar } from '@vercel/toolbar/next';
export default function MyApp({ Component, pageProps }) {
const isUserEmployee = useIsUserEmployee();
const shouldInjectToolbar =
process.env.NODE_ENV === 'development' || isUserEmployee;
return (
<>
<Component {...pageProps} />
{shouldInjectToolbar && <VercelToolbar />}
</>
);
}
Then, import and use the Next.js plugin in your next.config.js
:
// next.config.js
const withVercelToolbar = require('@vercel/toolbar/plugins/next')();
const nextConfig = {
...
}
module.exports = withVercelToolbar(nextConfig);
Now, when running next dev
you will see the Vercel toolbar and will be able to authenticate and interact with all the comments left in the preview environment of that branch.
You can configure some options for the plugin by passing an object in like:
const withVercelToolbar = require('@vercel/toolbar/plugins/next')({
devServerPort: 3123,
enableInProduction: false,
});
The available options are
devServerPort?: number
Port on which the toolbar's dev server will run locally (defaults to
43214
)
The toolbar runs a server locally to check the local git branch and watch for it to change, so it can reload the page and show the correct comments view
enableInProduction?: boolean
Defaults to
false
. Iftrue
the toolbar's dev server will run whenNODE_ENV === 'production'
.
See the documentation for more details.
FAQs
Vercel Toolbar
We found that @vercel/toolbar demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 9 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.