Build trying to compile every file in node_modules
#727
Comments
|
I just noticed its even trying to compile my tests too. |
|
This seems to be an issue with the static asset resolution. When I run Essentially, it's trying to compile every single file in the directory. |
|
OK, so the issue seems to be from the use of When I replace: with (static strings): to be used like so: then it compiles normally. This is a common usage - GitHub even recommends using |
|
Thanks for reporting this issue! Using Also note that ESM is not supported yet (see PR #720) |
|
Same behavior but with let given
tsconfig.json |
|
I tried to replicate the above scenarios with the following: test.mjs import fs from 'fs';
import path from 'path';
import { setFailed, getInput, info } from '@actions/core';
import mime from 'mime';
getInput('test');
var input = eval('user input');
path.resolve(input, 'myfile');running If you can provide a simple replication I can look into it further here. |
For some reason, whenever I run
ncc buildin my project, it seems to attempt to compile every file inside ofnode_modules, ie.This continues until I Control + C out of it.
This makes no sense to me, as the similar project with the exact same dependencies (I compared the
yarn.lockfiles) compiles with no problem.The
package.jsonof my project is as follows:The code itself is quite innocuous. The imports are as follows:
Is there anyone who has any idea why this could be happening?
The text was updated successfully, but these errors were encountered: