Issues with node-pg-migrate
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
Struggling to get https://github.com/salsita/node-pg-migrate
They seem to mix file loading approaches:
https://github.com/salsita/node-pg-migrate/blob/master/src/migration.ts#L23
works fine but it blows up when you get to:
https://github.com/salsita/node-pg-migrate/blob/master/src/runner.ts#L35
The relative paths come out wrong / the JS modules don't load.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the node-pg-migrate loading failure using the linked src/migration.ts and src/runner.ts locations. Check how relative paths and JavaScript modules are handled when compiling with ncc; done means node-pg-migrate loads successfully without the reported path or module errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100