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 🙏

© 2024 – Pkg Stats / Ryan Hefner

whatplatformis

v0.3.0

Published

[![npm](https://img.shields.io/npm/v/whatplatformis)](https://github.com/JiangWeixian/whatplatformis) [![GitHub](https://img.shields.io/npm/l/whatplatformis)](https://github.com/JiangWeixian/whatplatformis)

Downloads

6

Readme

whatplatformis

npm GitHub

why this repo

Thanks to nodejs condition exports feature, isServer will automatic be false in browser side, and be true in node side. It's friendly for bundler to make tree shaking work. No more runtime typeof window === 'undefined' check.

install

pnpm i whatplatformis

usage

import { isBrowser, isServer } from 'whatplatformis'

// isServer will be false in browser
// isBrowser will be true in browser

if (isServer) {
  // code...
}

Code under isServer will be automatic tree shaking in target browser bundled codes.

rollup

Build for target browser

// rollup.config.mjs
module.exports = {
  input: ['<entries>'],
  plugins: [
    // other plugins...
    resolve({
      browser: true,
    }),
  ],
}

Build for target node

// rollup.config.mjs
module.exports = {
  input: ['<entries>'],
  plugins: [
    // other plugins...
    resolve(),
  ],
}

Check example/rollup for more details.

swc

pnpm i swc-plugin-whatplatformis

add this plugin in .swcrc or swc-loader options

{
  "jsc": {
    "experimental": {
      "plugins": [
        [
          "swc-plugin-whatplatformis",
          {
            "target": "server",
            "packages": ["whatplatformis"],
            "isServerFns": []
          }
        ]
      ]
    }
  }
}

will replace isServer or isBrowser into bool. e.g. when target is server

before

import { isBrowser, isServer } from 'whatplatformis'

if (isServer) {
  console.log('isServer')
}

const target = isBrowser

after

import { isBrowser, isServer } from 'whatplatformis'

if (true) {
  console.log('isServer')
}

const target = false

options.target

  • type: "server" | "browser"

Control replace isBrowser | isServer into false | true

options.packages

  • type: string[]

Sometimes you maintain similar packages like whatplatformis, e.g. is-server, you can defined extra packages

{ "target": "server", "packages": ["whatplatformis", "is-server"] }

Plugin will also replace isServer and isBrowser from packages whatplatformis and is-server

options.isServerFns

  • type: string[]

[!WARNING]
serverFns ignore packages config, will not check where imported from, any package's isServreFns will be replaced into boolean.

Replace runtime isSSR() or isSSR?.() or namespace.isSSR() into true or false based on options.target.

FAQ

failed when webpack.splitChunks enabled

When splitChunks is enabled in webpack, whatplatformis maybe bundled into common chunks, should add plugin into plugin list to make tree shaking work.

import { WhatPlatformIsPlugin } from 'whatplatformis/webpack'

{
  // ...other configs
  plugins: [
    new WhatPlatformIsPlugin()
  ]
}

or use swc-plugin-whatplatformis if in swc world.

Check example/webpack for more details.

development

  • Setup - pnpm i
  • Build - pnpm build

built with ❤️ by 😼