Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Throws an error if called from module without parent / which only called itself #18

Closed
dummdidumm opened this issue Sep 2, 2020 · 1 comment · Fixed by #19
Closed

Comments

@dummdidumm
Copy link

dummdidumm commented Sep 2, 2020

I have the situation where after bundling with Rollup I get an error when trying to resolve a config file through cosmiconfig and traced the error back to this package.

In my situation, after bundling, the bundled file is the top level module and import-fresh and the packages it depends on are also in that same file. The call to parent-module then returns undefined because the call stack only consists of the file itself. The next call to resolve-from on the other hand expects the filePath to be a string and throws. I think falling back to the moduleId-path or __filename should be done instead.

I can reproduce this if I place the code of import-fresh in the same file and invoke it like this:

const path = require('path');
const resolveFrom = require('resolve-from');
const parentModule = require('parent-module');

// code of import-fresh ...

function a() {
    b();
}
function b() {
    c();
}
// repeat until....
function h() {
   importFresh('./doesnt-matter');
}
a();

Reproduced on Windows 10 with node v14.5.0

I'm still not sure if I'm doing something wrong elsewhere because your package is used by so many other packages and noone has opened this issue yet.

@JulienKode
Copy link
Contributor

We have the same issue in this GitHub Action: JulienKode/pull-request-name-linter-action#61

#19 can fix the issue I think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants