I am encountering an issue with my Javascript file not running due to a bigint error

Question

I am encountering an issue with my Javascript file not running due to a bigint error

I'm attempting to utilize @metaplex/js for NFT minting. Usually, my .js files function correctly, but when I execute the file, this particular error arises.

bigint: Failed to load bindings, pure JS will be used (try npm run rebuild?)

The meaning of this escapes me. Thus, I attempted to execute npm run rebuild, only to discover that 'rebuild' is a missing script and I couldn't locate a way to install it.

Below is my code snippet:

import { Connection, programs} from "@metaplex/js";
import { Loader } from "@solana/web3.js";
const { metadata: {Metadata}} = programs;

const connection = new Connection("devnet");
const tokenPublicKey = 'my_adress';

const run = async() => {
    try{
        const ownedMetadata = await Metadata.Loader(connection,tokenPublicKey)
        console.log(ownedMetadata)
    }
    catch{
        console.log('Failed to fetch')
    }

};

run();

If you have any insights or an explanation regarding the nature of my error, I would greatly appreciate it.

javascript npm solana metaplex

Answer 1

Answer №1

The error you are encountering is due to a nested dependency that includes a compilation step which may not be compatible with your platform. For more details, refer to this resource.

[...] The issue arises because one of the dependencies (bigint-buffer) undergoes a compilation process during installation, which can fail for various reasons. One common reason is the absence of necessary build tools on your system. While you can install these tools on Windows from here, it automatically switches to a pure JS solution if needed. Nevertheless, that warning message can indeed be quite annoying.

Despite the warning message, you should still be able to compile your code successfully.

Note that the existing JS SDK by Metaplex will soon be replaced by a new version: https://github.com/metaplex-foundation/js-next

Using the updated JS SDK, you can retrieve an NFT using the following code snippet:

import { Metaplex } from "@metaplex-foundation/js";
import { Connection, clusterApiUrl } from "@solana/web3.js";

const connection = new Connection(clusterApiUrl("mainnet-beta"));
const metaplex = new Metaplex(connection);
const mintAddress = new PublicKey("ATe3DymKZadrUoqAMn7HSpraxE4gB88uo1L9zLGmzJeL");

const nft = await metaplex.nfts().findByMint({ mintAddress });

Answer 2

The error you are encountering is due to a nested dependency that includes a compilation step which may not be compatible with your platform. For more details, refer to this resource.

[...] The issue arises because one of the dependencies (bigint-buffer) undergoes a compilation process during installation, which can fail for various reasons. One common reason is the absence of necessary build tools on your system. While you can install these tools on Windows from here, it automatically switches to a pure JS solution if needed. Nevertheless, that warning message can indeed be quite annoying.

Despite the warning message, you should still be able to compile your code successfully.

Note that the existing JS SDK by Metaplex will soon be replaced by a new version: https://github.com/metaplex-foundation/js-next

Using the updated JS SDK, you can retrieve an NFT using the following code snippet:

import { Metaplex } from "@metaplex-foundation/js";
import { Connection, clusterApiUrl } from "@solana/web3.js";

const connection = new Connection(clusterApiUrl("mainnet-beta"));
const metaplex = new Metaplex(connection);
const mintAddress = new PublicKey("ATe3DymKZadrUoqAMn7HSpraxE4gB88uo1L9zLGmzJeL");

const nft = await metaplex.nfts().findByMint({ mintAddress });

Answer 3

Answer №2

I encountered a similar issue recently while setting up acceptance tests in a Docker environment using a lightweight image based on node:21.4.0-bookworm-slim. The use of the *-slim tag indicates that the image contains only essential preinstalled packages.

FROM node:21.4.0-bookworm-slim

WORKDIR /code
COPY package* tsconfig.json /code
RUN npm install

Although the warning about bigint-buffer was not causing any failures, it raised performance concerns during test execution. To address this issue, I needed to eliminate these warnings from my terminal.

$ docker compose exec client npm run test:acceptance

> <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="295a4645484748044a45404c475d691807190719">[email protected]</a> test:acceptance
...

Even after running npm run rebuild as recommended, the problem persisted. Upon further investigation, I discovered that bigint-buffer relies on native C bindings for optimal performance, necessitating specific dependencies on the host system for successful compilation.

The build process is facilitated by node-gyp, which outlines the required dependencies in its documentation. In my Debian setup, installing python3 and build-essential before npm install resolved the issue:

RUN apt update \
    && apt install --assume-yes --no-install-recommends \
        build-essential \
        python3

If you're working locally, ensure to install comparable dependencies on your machine. The key is to have the necessary tools available to support native big number optimization without encountering any warnings.

Answer 4

I encountered a similar issue recently while setting up acceptance tests in a Docker environment using a lightweight image based on node:21.4.0-bookworm-slim. The use of the *-slim tag indicates that the image contains only essential preinstalled packages.

FROM node:21.4.0-bookworm-slim

WORKDIR /code
COPY package* tsconfig.json /code
RUN npm install

Although the warning about bigint-buffer was not causing any failures, it raised performance concerns during test execution. To address this issue, I needed to eliminate these warnings from my terminal.

$ docker compose exec client npm run test:acceptance

> <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="295a4645484748044a45404c475d691807190719">[email protected]</a> test:acceptance
...

Even after running npm run rebuild as recommended, the problem persisted. Upon further investigation, I discovered that bigint-buffer relies on native C bindings for optimal performance, necessitating specific dependencies on the host system for successful compilation.

The build process is facilitated by node-gyp, which outlines the required dependencies in its documentation. In my Debian setup, installing python3 and build-essential before npm install resolved the issue:

RUN apt update \
    && apt install --assume-yes --no-install-recommends \
        build-essential \
        python3

If you're working locally, ensure to install comparable dependencies on your machine. The key is to have the necessary tools available to support native big number optimization without encountering any warnings.

I am encountering an issue with my Javascript file not running due to a bigint error

Answer №1

Answer №2

Similar questions

Enhance the speed of my Tumblr page by using JavaScript for personalized styling tweaks

Encountered an issue retrieving tweets from the Twitter API 1.1

Utilizing Ajax to fetch a div element from a web page

Javascript is not functioning properly when making an ajax call

Difficulty encountered when trying to use Bootstrap tooltip with Bootstrap icon

Is it recommended for synchronous code invoked by a Promise's .then method to generate a fresh Promise

The local types package cannot be built by react-scripts even though tsc has successfully completed the process

The error message "MediaMetadata is not defined as no-undef and cannot be used as a constructor" appeared when trying to use MediaMetadata

I am looking to host several iterations of jQuery on a content delivery network within my Nuxt application

Experimenting with the input type generated by the Form Helper tool

How can I verify if an SVG file has a reliable source? (having troubles converting SVG to canvas)

Displaying an array within a method using Vue.js

Click the link to capture the ID and store it in a variable

Solving the challenges of creating a product index with JSON array using a combination of PHP, Javascript, and JSON

What is the best approach for writing a concise Select statement that produces a data list?

Trigger animation once you've scrolled past a designated point in the document

Retrieve a JSON WebMap using an ArcGIS JavaScript API Map object

Unlocking the secrets of obtaining post values using Body-parser in your Express Node.js application

How can I deactivate a Material UI button after it has been clicked once?

A step-by-step guide on how to fill a Vuetify select box with data retrieved from