[impit-node] Breaking Changes: Import Path & Headers Format in v0.8.2

[jlalmes]

Upgrading from impit@0.7.4 to impit@0.8.2 introduced two breaking changes that require code modifications:

1. Import path change: Must use 'impit/index.js' instead of 'impit'
2. Headers format change: Headers must be an array of tuples instead of an object

Issue 1: Import Path Breaking Change

Before (v0.7.4)

import { Impit, type ImpitResponse, type RequestInit } from 'impit';

After (v0.8.2)

import { Impit, type ImpitResponse, type RequestInit } from 'impit/index.js';

Impact: All imports break and require manual updates across the codebase.

Issue 2: Headers Format Breaking Change

Before (v0.7.4)

const res = await impit.fetch(url, {
  headers: {
    Accept: '*/*',
    'Accept-Language': 'en',
    ...otherHeaders,
  },
});

Error when using object format:

Error: Given napi value is not an array on RequestInit.headers

The error indicates that the native bindings expect an array format, but this is not documented and breaks the expected Web API fetch-like interface.

Workaround After (v0.8.2)

Currently using this workaround to maintain object-based header merging:

headers: Object.entries({
  Accept: '*/*',
  'Accept-Language': 'en',
  ...init.headers,
}) as [string, string][],

---

Thank you for maintaining this library!

[barjin]

Hello and thank you for your interest in this project!

I cannot reproduce the first issue locally - import { Impit } from 'impit' works just fine for me on Linux, with npm and impit@0.8.2.

The second issue is a consequence of your updated import path - the main script of impit is index.wrapper.js (see package.json below.

impit/impit-node/package.json

Line 5 in fdeaf3a

"main": "index.wrapper.js",

Can you please try reinstalling the package, checking your project setup and see if the problem persists?

Cheers!

[barjin]

Closing due to inactivity - let us know if the problem persists in a new project.

Cheers!