npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@surfside/ads-react

v0.1.18

Published

React components for Surfside Ads

Downloads

569

Readme

Core Library Elements

Design Architecture

The library follows a modern, modular React architecture with two primary layers:

  1. Provider: SurfsideProvider – Initializes the Surfside Ads SDK and manages shared global context.
  2. Hooks: Custom hooks that encapsulate ad fetching, rendering logic, state management, and analytics.

This separation of concerns allows for clean and extensible integration across a variety of use cases.

Quick Start

Installation

# Using npm
npm install @surfside/ads-react

# Using yarn
yarn add @surfside/ads-react

# Using bun
bun add @surfside/ads-react

Basic Usage

  1. Wrap your application with SurfsideProvider to provide the necessary context.
export default function App() {
    return (
        <html lang="en">
            <head>
                {/* Head Content */}
            </head>
            <body>
                <SurfsideProvider
                    channelId='XXXXX'
                    accountId='XXXXX'
                    siteId='XXXXX'
                    locationId='surfside-nyc'
                    userId='surfside-007'
                >
                    <div>
                        {/* Application Content */}
                    </div>
                </SurfsideProvider>
            </body>
        </html>
    );
}
  1. Render a banner ad using the useSurfsideBanner hook.
const Homepage = () => {
    const {
        banner,
        loading,
        error,
        analytics
    } = useSurfsideBanner({
        zoneId: 'XXXXX',
        size: [4,1 ]
    });

    useEffect(() => {
        analytics?.trackWin();
    }, [analytics]);

    if (loading) {
        return <BannerSkeleton/>;
    }

    if (error) {
        return <FallbackComponent/>;
    }

    return (
        <div>
            <h1>Welcome!</h1>
            <MenuBar/>
            {/* Banner Ad right below the menu bar */}
            <div dangerouslySetInnerHTML={{__html: banner.adm}}></div>
            {/* ... webpage content */}
        </div>
    );
};

Where to start

Follow these guides to set up your Surfside Ads implementation

Performance & Compatibility

The @surfside/ads-react library is designed to be client-side only. All hooks and rendering logic must run in the browser as access to the browser API is required for bid requests to function correctly. Server-side rendering (SSR) is not supported yet, and attempting to use hooks or providers on the server will result in runtime errors.

To avoid hydration issues, always ensure components using Surfside hooks are rendered only after the client has mounted.

const IsClientOnly = ({ children }: { children: React.ReactNode }) => {
    const [ready, setReady] = React.useState(false);
    React.useEffect(() => setReady(true), []);
    return ready ? <>{children}</> : null;
};

You can wrap Surfside components in a guard like this if needed.

License

Copyright © 2025 Surfside. All rights reserved.