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
This might be more of an IDE or Node.js issue, but it's stumped me for a while.
As stated in the docs, when using yalc link a symlink is created in the project's node_modules directory which points to the project's .yalc/<some lib> directory. For my situation, this works great as I do not want to modify the project's package.json file.
The issue I'm having is withimport statements and type definitions. import statements do resolve, so this might be a pure IDE issue, but if instead of "linking" the Yalc dependency I use yalc add, the aforementioned issues don't occur.
Environment:
This might be more of an IDE or Node.js issue, but it's stumped me for a while.
As stated in the docs, when using
yalc link
a symlink is created in the project'snode_modules
directory which points to the project's.yalc/<some lib>
directory. For my situation, this works great as I do not want to modify the project'spackage.json
file.The issue I'm having is with
import
statements and type definitions.import
statements do resolve, so this might be a pure IDE issue, but if instead of "linking" the Yalc dependency I useyalc add
, the aforementioned issues don't occur.This is the build process that I'm following:
The text was updated successfully, but these errors were encountered: