Question

186

Rollup.js unresolved dependencies

rated 0 times [ 192] [ 6] / answers: 1 / hits: 36025 / 8 Years ago, thu, january 5, 2017, 12:00:00

I am trying to incorporate rollup.js into a project. Currently I am getting the warnings provided below in the console (unresolved dependencies) and I am not sure why or how to fix it:

'fs' is imported by node_modulesfilereaderFileReader.js, but could not be resolved – treating it as an external dependency



'fs' is imported by  commonjs-external:fs, but could not be resolved – treating it as an external dependency



preferring built-in module 'punycode' over local alternative at 'C:UsersRyanOneDriveProjectsCustom CodingZapierRyan Testnode_modulespunycodepunycode.js', pass 'preferBuiltins: false' to disable this behavior or 'preferBuiltins: true' to disable this warning



preferring built-in module 'punycode' over local alternative at 'C:UsersRyanOneDriveProjectsCustom CodingZapierRyan Testnode_modulespunycodepunycode.js', pass 'preferBuiltins: false' to disable this behavior or 'preferBuiltins: true' to disable this warning

Here is the test.js script requiring FileReader and https:

var FileReader = require('filereader');

var https = require('https');

Finally the rollup.config.js file which executes creating the bundle:

var rollup = require('rollup');



var commonjs = require('rollup-plugin-commonjs');

var nodeResolve = require('rollup-plugin-node-resolve');

var globals = require('rollup-plugin-node-globals');

var builtins = require('rollup-plugin-node-builtins');



// build bundle

rollup

  .rollup({

    entry: 'test.js',

    plugins: [

      nodeResolve(),

      commonjs(),

      globals(),

      builtins()

    ]

  })

  .then(bundle => bundle.write({

    dest: 'rollupBundle/bundle.js',

    format: 'cjs'

  }))

  .catch(err => console.log(err.stack));

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

megb

Add To Favorites

Follow

Total Points: 230

Total Questions: 113

Total Answers: 100

Location: Tokelau

Member since Sun, May 7, 2023

1 Year ago

answered 8 Years ago jamaal · Accepted Answer

The CLI will generate more informative warnings — if you update your config file to use the standard form, then you can use rollup -c instead and it will often give you a URL to help diagnose issues.

Here's a config file with the necessary changes to squelch those warnings:

import commonjs from 'rollup-plugin-commonjs';

import nodeResolve from 'rollup-plugin-node-resolve';

import globals from 'rollup-plugin-node-globals';

import builtins from 'rollup-plugin-node-builtins';



export default {

  entry: 'test.js',

  dest: 'rollupBundle/bundle.js',

  format: 'cjs',

  external: [ 'fs' ], // tells Rollup 'I know what I'm doing here'

  plugins: [

    nodeResolve({ preferBuiltins: false }), // or `true`

    commonjs(),

    globals(),

    builtins()

  ]

};

UPDATE: The "official" Rollup plugins are now under the @rollup namespace on npm, if you install the two versions mentioned above you will get an "npm WARN deprecated" message, so instead install the newer versions instead:

npm install @rollup/plugin-commonjs --save-dev

npm install @rollup/plugin-node-resolve --save-dev

then use them like this:

import commonjs from '@rollup/plugin-commonjs';

import { nodeResolve } from '@rollup/plugin-node-resolve';