You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Referring to the javascript-astar source code, this warning is correct since main is set twice in its package.json. However, this warning is seemingly useless when coming from an external dependency. In our build script, using the JavaScript API, we were able to go with the second option from this comment on a similar issue and suppress this warning for our builds.
For running our unit tests using karma, we are unable to access the API in the same fashion leading to the warnings being printed out each time our application is rebuilt. The only option to silence this warning in this scenario is to set logLevel: 'error' which will hide all of the warnings. We would like to avoid this if possible.
If possible, could this type of warning be ignored by esbuild when coming from node_modules?
The text was updated successfully, but these errors were encountered:
While bundling we are running into the following warning:
Referring to the javascript-astar source code, this warning is correct since main is set twice in its package.json. However, this warning is seemingly useless when coming from an external dependency. In our build script, using the JavaScript API, we were able to go with the second option from this comment on a similar issue and suppress this warning for our builds.
For running our unit tests using karma, we are unable to access the API in the same fashion leading to the warnings being printed out each time our application is rebuilt. The only option to silence this warning in this scenario is to set
logLevel: 'error'
which will hide all of the warnings. We would like to avoid this if possible.If possible, could this type of warning be ignored by esbuild when coming from
node_modules
?The text was updated successfully, but these errors were encountered: