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
In the development of thorest package v2, we are currently importing modules from v1 using the published NPM packages. However, this causes issues when making changes to these packages in v2 because the imports resolve locally instead of pulling from the NPM package.
To resolve this, we need to update the package.json files to point to core package v2 instead of using the v1. This ensures that changes made to the dependencies in the v2 branch are properly reflected in our development environment.
Tasks:
Update all relevant package.json files to reference the v2 for dependencies instead of v1
Ensure that dependencies resolve correctly and that local development workflows remain functional.
Test the changes to confirm they work as expected.
Expected Outcome:
Dependencies should correctly pull from the v2 core sdk package, allowing us to develop and test changes without conflicts caused by local resolution.
The text was updated successfully, but these errors were encountered:
Summary
In the development of thorest package v2, we are currently importing modules from v1 using the published NPM packages. However, this causes issues when making changes to these packages in v2 because the imports resolve locally instead of pulling from the NPM package.
To resolve this, we need to update the package.json files to point to core package v2 instead of using the v1. This ensures that changes made to the dependencies in the v2 branch are properly reflected in our development environment.
Tasks:
Expected Outcome:
Dependencies should correctly pull from the v2 core sdk package, allowing us to develop and test changes without conflicts caused by local resolution.
The text was updated successfully, but these errors were encountered: