-
Notifications
You must be signed in to change notification settings - Fork 2
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
build: use NPM packages instead of git submodules #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this is great.
We can also install forge-std
as a Node.js package from GitHub.
0b1fd65
to
73b76ec
Compare
I've asked about this here My personal opinion is that we could leave the |
I wasn't able to use Forge Std as a Node.js package, so I think this is not a question of preference but of necessity. We will keep installing Forge Std from git submodules. |
73b76ec
to
e73aa1e
Compare
I don't think you have updated the It shouldn't be a "necessity": @forge-std/=node_modules/@forge-std/"
import { Test } from "@forge-std/src/Test.sol" |
|
I think I did: https://github.com/sablier-labs/sablier-v2-integration-template/actions/runs/6668745614 |
Don't think you looked at the latest CI run, @andreivladbrg. |
Still not a "necessity". This can be fixed by adding this remappings. You can run locally this branch: https://app.warp.dev/block/MtrSbAaMRDnU5ZrsyFFLul A easier fix would be to import in Anyway, I am not in favor in installing forge-std as NPM, as said in my initial comment. |
Ah, yes. Remappings for DSTest! Good point. |
Switches from installing
v2-core
as a git module to installing it as a NPM package.