Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bad paths after bundling with rollup following react 18 upgrade

Open
#752 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, react, rollup

Research direction

Start by comparing the React 17 and React 18 bundled index.js examples and inspect the Rollup configuration. Trace how imports from ./utils/domFns, ./utils/positionFns, ./utils/shims, and ./utils/log are emitted after the React 18 upgrade. Done means the bundled output no longer requires the unbundled /utils/ directory.

Written by the indexing model from the issue text.

Description

Hey, so perhaps this is an issue with my rollup configuration but I thought this would be the best place to post. After upgrading to react 18, the resulting bundled file is looking for a /utils/ directory, which is part of the un-bundled react-draggable module. I'm not seeing a clear way to get the contents of utils to properly bundle as they naturally did in react 17.

Before the upgrade the resulting bundle index.js (react 17)

var _positionFns = positionFns;
var _shims = shims;
var _DraggableCore = _interopRequireDefault(DraggableCore);
var _log = _interopRequireDefault(log);

After the upgrade the resulting bundle index.js (react 18)

var _positionFns = require("./utils/positionFns");
var _shims = require("./utils/shims");
var _DraggableCore = _interopRequireDefault(require("./DraggableCore"));
var _log = _interopRequireDefault(require("./utils/log"));
Dominant language
JavaScript
Stars
9.3k
Forks
1k
Avg merge
3d 8h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from react-grid-layout/react-draggable

All issues in react-grid-layout/react-draggable

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.