Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions jest.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ module.exports = {
'json',
'node',
],
modulePathIgnorePatterns: ['<rootDir>/.metamask/cache/java-tron-up/'],
// The path to the Prettier executable used to format snapshots
// Jest doesn't support Prettier 3 yet, so we use Prettier 2
prettierPath: require.resolve('prettier-2'),
Expand Down
4 changes: 4 additions & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,9 @@
"webpack:lavamoat:policy:mv2": "concurrently 'yarn webpack:lavamoat:build:mv2 --generatePolicy' 'yarn webpack:lavamoat:build:mv2 --generatePolicy --type flask' 'yarn webpack:lavamoat:build:mv2 --generatePolicy --type beta' 'yarn webpack:lavamoat:build:mv2 --generatePolicy --type experimental' --kill-others-on-fail",
"webpack:lavamoat:policy:mv3": "concurrently 'yarn webpack:lavamoat:build --generatePolicy' 'yarn webpack:lavamoat:build --generatePolicy --type flask' 'yarn webpack:lavamoat:build --generatePolicy --type beta' 'yarn webpack:lavamoat:build --generatePolicy --type experimental' --kill-others-on-fail",
"foundryup": "yarn mm-foundryup",
"java-tron": "node_modules/.bin/java-tron",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you please explain the purpose of each new scripts for tron ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea of this script is to be a Tron equivalent to foundryup. It uses a package to manage a local Java Tron node that is started to power our E2E tests instead of mocking everything

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am curios why its 3 new scripts: java-tron, java-tron-up, java-tron-up:install

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, yeah actually now that I think about it the install one is not really needed. It's syntactic sugar for java-tron-up passing an install parameter

"java-tron-up": "node_modules/.bin/java-tron-up",
"java-tron-up:install": "yarn java-tron-up install",
"postinstall": "node -e \"process.exit(process.env.CI ? 0 : 1)\" || (yarn webpack:clearcache && yarn foundryup && yarn skills:postinstall)",
"skills": "metamask-skills sync",
"skills:postinstall": "metamask-skills postinstall",
Expand Down Expand Up @@ -587,6 +590,7 @@
"@metamask/eth-json-rpc-provider": "^6.0.0",
"@metamask/forwarder": "^1.1.0",
"@metamask/foundryup": "^1.0.1",
"@metamask/java-tron-up": "^1.0.0",
"@metamask/messenger-cli": "^0.1.0",
"@metamask/phishing-warning": "^5.1.0",
"@metamask/preferences-controller": "^23.0.0",
Expand Down
Loading
Loading