2016-12-16 21:43:37 +01:00
|
|
|
npm-debug.log
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
|
|
|
yarn-error.log
|
2015-08-01 03:38:02 +02:00
|
|
|
node_modules
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
|
|
|
package-lock.json
|
2017-06-12 22:30:59 +02:00
|
|
|
|
2019-07-25 00:54:16 +02:00
|
|
|
audit.json
|
|
|
|
|
|
2015-08-01 03:38:02 +02:00
|
|
|
app/bower_components
|
|
|
|
|
test/bower_components
|
|
|
|
|
package
|
2021-03-31 17:19:03 +02:00
|
|
|
.eslintcache
|
2017-06-12 22:30:59 +02:00
|
|
|
|
2018-03-10 03:56:39 +01:00
|
|
|
# IDEs
|
2017-11-24 02:33:44 +01:00
|
|
|
.idea
|
2018-03-10 03:56:39 +01:00
|
|
|
.vscode
|
2018-05-28 23:29:31 +02:00
|
|
|
.sublime-project
|
2017-11-24 02:33:44 +01:00
|
|
|
|
2019-07-18 07:51:47 +02:00
|
|
|
*.bak
|
|
|
|
|
|
2018-07-21 01:00:41 +02:00
|
|
|
# VIM
|
|
|
|
|
*.swp
|
|
|
|
|
*.swo
|
|
|
|
|
|
2017-06-12 22:30:59 +02:00
|
|
|
temp
|
|
|
|
|
.tmp
|
|
|
|
|
.sass-cache
|
2016-03-29 23:31:25 +02:00
|
|
|
.DS_Store
|
2017-06-12 22:30:59 +02:00
|
|
|
app/.DS_Store
|
|
|
|
|
|
2021-02-04 15:30:22 +01:00
|
|
|
storybook-build/
|
2018-09-11 17:56:05 +02:00
|
|
|
coverage/
|
2021-04-09 19:20:32 +02:00
|
|
|
jest-coverage/
|
2017-06-12 22:30:59 +02:00
|
|
|
dist
|
2016-03-29 23:31:25 +02:00
|
|
|
builds/
|
2016-08-22 20:59:26 +02:00
|
|
|
builds.zip
|
Add TypeScript migration dashboard (#13820)
As we convert parts of the codebase to TypeScript, we will want a way to
track progress. This commit adds a dashboard which displays all of the
files that we wish to convert to TypeScript and which files we've
already converted.
The list of all possible files to convert is predetermined by walking
the dependency graph of each entrypoint the build system uses to compile
the extension (the files that the entrypoint imports, the files that the
imports import, etc). The list should not need to be regenerated, but
you can do it by running:
yarn ts-migration:enumerate
The dashboard is implemented as a separate React app. The CircleCI
configuration has been updated so that when a new commit is pushed, the
React app is built and stored in the CircleCI artifacts. When a PR is
merged, the built files will be pushed to a separate repo whose sole
purpose is to serve the dashboard via GitHub Pages (this is the same
way that the Storybook works). All of the app code and script to build
the app are self-contained under
`development/ts-migration-dashboard`. To build this app yourself, you
can run:
yarn ts-migration:dashboard:build
or if you want to build automatically as you change files, run:
yarn ts-migration:dashboard:watch
Then open the following file in your browser (there is no server
component):
development/ts-migration-dashboard/build/index.html
Finally, although you shouldn't have to do this, to manually deploy the
dashboard once built, you can run:
git remote add ts-migration-dashboard git@github.com:MetaMask/metamask-extension-ts-migration-dashboard.git
yarn ts-migration:dashboard:deploy
2022-08-09 22:16:08 +02:00
|
|
|
development/ts-migration-dashboard/build
|
|
|
|
|
development/ts-migration-dashboard/intermediate
|
2017-06-12 22:30:59 +02:00
|
|
|
|
2018-03-29 22:49:54 +02:00
|
|
|
test-artifacts
|
2018-06-11 20:04:28 +02:00
|
|
|
test-builds
|
2020-07-30 18:55:56 +02:00
|
|
|
build-artifacts
|
2018-03-29 22:49:54 +02:00
|
|
|
|
2017-08-06 22:46:49 +02:00
|
|
|
#ignore css output and sourcemaps
|
2021-04-28 21:53:59 +02:00
|
|
|
ui/css/output/
|
2017-08-06 22:27:07 +02:00
|
|
|
|
2017-07-24 06:32:49 +02:00
|
|
|
notes.txt
|
|
|
|
|
|
2018-06-11 20:04:28 +02:00
|
|
|
.nyc_output
|
2020-05-15 21:40:06 +02:00
|
|
|
|
Add validation to production build script (#15468)
Validation has been added to the build script when the "prod" target is
selected. We now ensure that all expected environment variables are
set, and that no extra environment variables are present (which might
indicate that the wrong configuration file is being used).
The `prod` target uses a new `.metamaskprodrc` configuration file. Each
required variable can be specified either via environment variable or
via this config file. CI will continue set these via environment
variable, but for local manual builds we can use the config file to
simplify the build process and ensure consistency.
A new "dist" target has been added to preserve the ability to build a
"production-like" build without this validation.
The config validation is invoked early in the script, in the CLI
argument parsing step, so that it would fail more quickly. Otherwise
we'd have to wait a few minutes longer for the validation to run.
This required some refactoring, moving functions to the utility module
and moving the config to a dedicated module.
Additionally, support has been added for all environment variables to
be set via the config file. Previously the values `PUBNUB_PUB_KEY`,
`PUBNUB_SUB_KEY`, `SENTRY_DSN`, and `SWAPS_USE_DEV_APIS` could only be
set via environment variable. Now, all of these variables can be set
either way.
Closes #15003
2022-08-19 20:16:18 +02:00
|
|
|
# MetaMask configuration
|
2020-05-15 21:40:06 +02:00
|
|
|
.metamaskrc
|
Add validation to production build script (#15468)
Validation has been added to the build script when the "prod" target is
selected. We now ensure that all expected environment variables are
set, and that no extra environment variables are present (which might
indicate that the wrong configuration file is being used).
The `prod` target uses a new `.metamaskprodrc` configuration file. Each
required variable can be specified either via environment variable or
via this config file. CI will continue set these via environment
variable, but for local manual builds we can use the config file to
simplify the build process and ensure consistency.
A new "dist" target has been added to preserve the ability to build a
"production-like" build without this validation.
The config validation is invoked early in the script, in the CLI
argument parsing step, so that it would fail more quickly. Otherwise
we'd have to wait a few minutes longer for the validation to run.
This required some refactoring, moving functions to the utility module
and moving the config to a dedicated module.
Additionally, support has been added for all environment variables to
be set via the config file. Previously the values `PUBNUB_PUB_KEY`,
`PUBNUB_SUB_KEY`, `SENTRY_DSN`, and `SWAPS_USE_DEV_APIS` could only be
set via environment variable. Now, all of these variables can be set
either way.
Closes #15003
2022-08-19 20:16:18 +02:00
|
|
|
.metamaskprodrc
|
2022-03-21 19:54:47 +01:00
|
|
|
|
|
|
|
|
# TypeScript
|
|
|
|
|
tsout/
|
2022-09-23 18:38:40 +02:00
|
|
|
|
|
|
|
|
# Test results
|
2022-11-24 20:59:07 +01:00
|
|
|
test-results/
|
|
|
|
|
|
|
|
|
|
# This file is used to authenticate with the GitHub Package registry, to
|
|
|
|
|
# enable the use of @metamask preview builds.
|
|
|
|
|
.npmrc
|
