feat(api): api update (#24)

Author: Stainless Bot

CONTRIBUTING.md

@@ -55,12 +55,12 @@ $ cd sdk-node
 # With yarn
 $ yarn link
 $ cd ../my-package
-$ yarn link @browserbasehq/sdk
+$ yarn link browserbase
 
 # With pnpm
 $ pnpm link --global
 $ cd ../my-package
-$ pnpm link -—global @browserbasehq/sdk
+$ pnpm link -—global browserbase
 ```
 
 ## Running tests

README.md

@@ -1,6 +1,6 @@
 # Browserbase Node API Library
 
-[![NPM version](https://img.shields.io/npm/v/@browserbasehq/sdk.svg)](https://npmjs.org/package/@browserbasehq/sdk) ![npm bundle size](https://img.shields.io/bundlephobia/minzip/@browserbasehq/sdk)
+[![NPM version](https://img.shields.io/npm/v/browserbase.svg)](https://npmjs.org/package/browserbase) ![npm bundle size](https://img.shields.io/bundlephobia/minzip/browserbase)
 
 This library provides convenient access to the Browserbase REST API from server-side TypeScript or JavaScript.
 
@@ -11,16 +11,19 @@ It is generated with [Stainless](https://www.stainlessapi.com/).
 ## Installation
 
 ```sh
-npm install @browserbasehq/sdk
+npm install git+ssh://[email protected]:browserbase/sdk-node.git
 ```
 
+> [!NOTE]
+> Once this package is [published to npm](https://app.stainlessapi.com/docs/guides/publish), this will become: `npm install browserbase`
+
 ## Usage
 
 The full API of this library can be found in [api.md](api.md).
 
 <!-- prettier-ignore -->
 ```js
-import Browserbase from '@browserbasehq/sdk';
+import Browserbase from 'browserbase';
 
 const client = new Browserbase({
   apiKey: process.env['BROWSERBASE_API_KEY'], // This is the default and can be omitted
@@ -41,7 +44,7 @@ This library includes TypeScript definitions for all request params and response
 
 <!-- prettier-ignore -->
 ```ts
-import Browserbase from '@browserbasehq/sdk';
+import Browserbase from 'browserbase';
 
 const client = new Browserbase({
   apiKey: process.env['BROWSERBASE_API_KEY'], // This is the default and can be omitted
@@ -215,11 +218,11 @@ add the following import before your first import `from "Browserbase"`:
 ```ts
 // Tell TypeScript and the package to use the global web fetch instead of node-fetch.
 // Note, despite the name, this does not add any polyfills, but expects them to be provided if needed.
-import '@browserbasehq/sdk/shims/web';
-import Browserbase from '@browserbasehq/sdk';
+import 'browserbase/shims/web';
+import Browserbase from 'browserbase';
 ```
 
-To do the inverse, add `import "@browserbasehq/sdk/shims/node"` (which does import polyfills).
+To do the inverse, add `import "browserbase/shims/node"` (which does import polyfills).
 This can also be useful if you are getting the wrong TypeScript types for `Response` ([more details](https://github.com/browserbase/sdk-node/tree/main/src/_shims#readme)).
 
 ### Logging and middleware
@@ -229,7 +232,7 @@ which can be used to inspect or alter the `Request` or `Response` before/after e
 
 ```ts
 import { fetch } from 'undici'; // as one example
-import Browserbase from '@browserbasehq/sdk';
+import Browserbase from 'browserbase';
 
 const client = new Browserbase({
   fetch: async (url: RequestInfo, init?: RequestInit): Promise<Response> => {

jest.config.ts

@@ -7,9 +7,9 @@ const config: JestConfigWithTsJest = {
     '^.+\\.(t|j)sx?$': ['@swc/jest', { sourceMaps: 'inline' }],
   },
   moduleNameMapper: {
-    '^@browserbasehq/sdk$': '<rootDir>/src/index.ts',
-    '^@browserbasehq/sdk/_shims/auto/(.*)$': '<rootDir>/src/_shims/auto/$1-node',
-    '^@browserbasehq/sdk/(.*)$': '<rootDir>/src/$1',
+    '^browserbase$': '<rootDir>/src/index.ts',
+    '^browserbase/_shims/auto/(.*)$': '<rootDir>/src/_shims/auto/$1-node',
+    '^browserbase/(.*)$': '<rootDir>/src/$1',
   },
   modulePathIgnorePatterns: [
     '<rootDir>/ecosystem-tests/',

package.json

@@ -66,8 +66,8 @@
     "./shims/web.mjs"
   ],
   "imports": {
-    "@browserbasehq/sdk": ".",
-    "@browserbasehq/sdk/*": "./src/*"
+    "browserbase": ".",
+    "browserbase/*": "./src/*"
   },
   "exports": {
     "./_shims/auto/*": {

scripts/build

@@ -8,7 +8,7 @@ node scripts/utils/check-version.cjs
 
 # Build into dist and will publish the package from there,
 # so that src/resources/foo.ts becomes <package root>/resources/foo.js
-# This way importing from `"@browserbasehq/sdk/resources/foo"` works
+# This way importing from `"browserbase/resources/foo"` works
 # even with `"moduleResolution": "node"`
 
 rm -rf dist; mkdir dist
@@ -47,8 +47,8 @@ node scripts/utils/postprocess-files.cjs
 
 # make sure that nothing crashes when we require the output CJS or
 # import the output ESM
-(cd dist && node -e 'require("@browserbasehq/sdk")')
-(cd dist && node -e 'import("@browserbasehq/sdk")' --input-type=module)
+(cd dist && node -e 'require("browserbase")')
+(cd dist && node -e 'import("browserbase")' --input-type=module)
 
 if command -v deno &> /dev/null && [ -e ./scripts/build-deno ]
 then

scripts/utils/postprocess-files.cjs

@@ -2,7 +2,7 @@ const fs = require('fs');
 const path = require('path');
 const { parse } = require('@typescript-eslint/parser');
 
-const pkgImportPath = process.env['PKG_IMPORT_PATH'] ?? '@browserbasehq/sdk/';
+const pkgImportPath = process.env['PKG_IMPORT_PATH'] ?? 'browserbase/';
 
 const distDir =
   process.env['DIST_PATH'] ?
@@ -142,7 +142,7 @@ async function postprocess() {
 
     if (file.endsWith('.d.ts')) {
       // work around bad tsc behavior
-      // if we have `import { type Readable } from '@browserbasehq/sdk/_shims/index'`,
+      // if we have `import { type Readable } from 'browserbase/_shims/index'`,
       // tsc sometimes replaces `Readable` with `import("stream").Readable` inline
       // in the output .d.ts
       transformed = transformed.replace(/import\("stream"\).Readable/g, 'Readable');

src/_shims/README.md

@@ -1,9 +1,9 @@
 # 👋 Wondering what everything in here does?
 
-`@browserbasehq/sdk` supports a wide variety of runtime environments like Node.js, Deno, Bun, browsers, and various
+`browserbase` supports a wide variety of runtime environments like Node.js, Deno, Bun, browsers, and various
 edge runtimes, as well as both CommonJS (CJS) and EcmaScript Modules (ESM).
 
-To do this, `@browserbasehq/sdk` provides shims for either using `node-fetch` when in Node (because `fetch` is still experimental there) or the global `fetch` API built into the environment when not in Node.
+To do this, `browserbase` provides shims for either using `node-fetch` when in Node (because `fetch` is still experimental there) or the global `fetch` API built into the environment when not in Node.
 
 It uses [conditional exports](https://nodejs.org/api/packages.html#conditional-exports) to
 automatically select the correct shims for each environment. However, conditional exports are a fairly new
@@ -15,32 +15,32 @@ getting the wrong raw `Response` type from `.asResponse()`, for example.
 
 The user can work around these issues by manually importing one of:
 
-- `import '@browserbasehq/sdk/shims/node'`
-- `import '@browserbasehq/sdk/shims/web'`
+- `import 'browserbase/shims/node'`
+- `import 'browserbase/shims/web'`
 
 All of the code here in `_shims` handles selecting the automatic default shims or manual overrides.
 
 ### How it works - Runtime
 
-Runtime shims get installed by calling `setShims` exported by `@browserbasehq/sdk/_shims/registry`.
+Runtime shims get installed by calling `setShims` exported by `browserbase/_shims/registry`.
 
-Manually importing `@browserbasehq/sdk/shims/node` or `@browserbasehq/sdk/shims/web`, calls `setShims` with the respective runtime shims.
+Manually importing `browserbase/shims/node` or `browserbase/shims/web`, calls `setShims` with the respective runtime shims.
 
-All client code imports shims from `@browserbasehq/sdk/_shims/index`, which:
+All client code imports shims from `browserbase/_shims/index`, which:
 
 - checks if shims have been set manually
-- if not, calls `setShims` with the shims from `@browserbasehq/sdk/_shims/auto/runtime`
-- re-exports the installed shims from `@browserbasehq/sdk/_shims/registry`.
+- if not, calls `setShims` with the shims from `browserbase/_shims/auto/runtime`
+- re-exports the installed shims from `browserbase/_shims/registry`.
 
-`@browserbasehq/sdk/_shims/auto/runtime` exports web runtime shims.
-If the `node` export condition is set, the export map replaces it with `@browserbasehq/sdk/_shims/auto/runtime-node`.
+`browserbase/_shims/auto/runtime` exports web runtime shims.
+If the `node` export condition is set, the export map replaces it with `browserbase/_shims/auto/runtime-node`.
 
 ### How it works - Type time
 
-All client code imports shim types from `@browserbasehq/sdk/_shims/index`, which selects the manual types from `@browserbasehq/sdk/_shims/manual-types` if they have been declared, otherwise it exports the auto types from `@browserbasehq/sdk/_shims/auto/types`.
+All client code imports shim types from `browserbase/_shims/index`, which selects the manual types from `browserbase/_shims/manual-types` if they have been declared, otherwise it exports the auto types from `browserbase/_shims/auto/types`.
 
-`@browserbasehq/sdk/_shims/manual-types` exports an empty namespace.
-Manually importing `@browserbasehq/sdk/shims/node` or `@browserbasehq/sdk/shims/web` merges declarations into this empty namespace, so they get picked up by `@browserbasehq/sdk/_shims/index`.
+`browserbase/_shims/manual-types` exports an empty namespace.
+Manually importing `browserbase/shims/node` or `browserbase/shims/web` merges declarations into this empty namespace, so they get picked up by `browserbase/_shims/index`.
 
-`@browserbasehq/sdk/_shims/auto/types` exports web type definitions.
-If the `node` export condition is set, the export map replaces it with `@browserbasehq/sdk/_shims/auto/types-node`, though TS only picks this up if `"moduleResolution": "nodenext"` or `"moduleResolution": "bundler"`.
+`browserbase/_shims/auto/types` exports web type definitions.
+If the `node` export condition is set, the export map replaces it with `browserbase/_shims/auto/types-node`, though TS only picks this up if `"moduleResolution": "nodenext"` or `"moduleResolution": "bundler"`.

src/_shims/index.d.ts

@@ -2,7 +2,7 @@
  * Disclaimer: modules in _shims aren't intended to be imported by SDK users.
  */
 import { manual } from './manual-types';
-import * as auto from '@browserbasehq/sdk/_shims/auto/types';
+import * as auto from 'browserbase/_shims/auto/types';
 import { type RequestOptions } from '../core';
 
 type SelectType<Manual, Auto> = unknown extends Manual ? Auto : Manual;

src/_shims/index.js

@@ -2,7 +2,7 @@
  * Disclaimer: modules in _shims aren't intended to be imported by SDK users.
  */
 const shims = require('./registry');
-const auto = require('@browserbasehq/sdk/_shims/auto/runtime');
+const auto = require('browserbase/_shims/auto/runtime');
 if (!shims.kind) shims.setShims(auto.getRuntime(), { auto: true });
 for (const property of Object.keys(shims)) {
   Object.defineProperty(exports, property, {

src/_shims/index.mjs

@@ -2,6 +2,6 @@
  * Disclaimer: modules in _shims aren't intended to be imported by SDK users.
  */
 import * as shims from './registry.mjs';
-import * as auto from '@browserbasehq/sdk/_shims/auto/runtime';
+import * as auto from 'browserbase/_shims/auto/runtime';
 if (!shims.kind) shims.setShims(auto.getRuntime(), { auto: true });
 export * from './registry.mjs';