Update lavamoat browserify docs#476
Conversation
9d28481 to
86599cf
Compare
- Fix examples link - Fix resolve/lib/sync.js throws error it can't find lavamoat-browserify from node_modules - Install lavamoat-browserify with Yarn before running lavamoat - Fix yarn start server broken MM logo if user forgets to run yarn lavamoat first - Error: LavaMoat - required package not in allowlist: package "metamask-logo" requested "metamask-logo>gl-mat4" as "gl-mat4/perspective" - i.e. Run yarn lavamoat to fully update policy.json we provide - Update remaining examples documentation, files and deps
86599cf to
25a8dba
Compare
| { | ||
| "resources": { | ||
| } | ||
| } No newline at end of file |
There was a problem hiding this comment.
updated here like
There was a problem hiding this comment.
we could omit our policy configs and rely on running yarn lavamoat in instructions to autogen
There was a problem hiding this comment.
added to both examples in 4bd9640
but i noticed yarn lavamoat always removes missing EOF newlines in policy.json
There was a problem hiding this comment.
if we intend to be consistent can revert this commit
or follow-up with lavamoat cli to add missing newlines in both policy configs
(atm policy-override.json isn't formatted if it exists)
| }, | ||
| "dependencies": { | ||
| "metamask-logo": "^2.2.1" | ||
| "lavamoat-browserify": "^16.0.0", |
There was a problem hiding this comment.
this would be a devDependency i think?
| }, | ||
| "dependencies": { | ||
| "metamask-logo": "^2.2.1" | ||
| "lavamoat-browserify": "^16.0.0", |
There was a problem hiding this comment.
this would be a devDependency i think?
There was a problem hiding this comment.
Did you experience problems running these examples? I test my code against example
01constantly, never experiencing any problems..
just making sure @weizman you're adding lavamoat-browserify too right in this example 🤔
i checked yarn global add lavamoat-browserify@15.5.0 (since 16 was wrongly introduced) but it has no binaries
There was a problem hiding this comment.
@leotm lavamoat-browserify is not supposed to have any binaries AFAIK - what are you missing specifically?
There was a problem hiding this comment.
|
I'm confused about the general motivation here. Did you experience problems running these examples? |
|
I think I might understand the confusion here.. I'm pretty sure you see errors because of the extensions you have installed while testing this page. |
perfect thanks exactly right its my extensions ^ can confirm no console.errors incognito |
yep exactly was wondering where the examples link supposed to go to and why couldn't run the js example or cli one then was curious why and why we commit so thought this PR might address those problems i ran into |
Co-authored-by: weizman <weizmangal@gmail.com>
And update documentation
And prettify js example
legobeat
left a comment
There was a problem hiding this comment.
one small suggestion, lgtm otherwise!
Co-authored-by: legobeat <109787230+legobeat@users.noreply.github.com>
- fix: Node.js 18 compatibility (LavaMoat#551) - deps: update lavamoat-core@^12.4.0->^14.1.1 - deps: @lavamoat/lavapack@^3.3.0->^5.1.2 - doc: update examples and docs (LavaMoat#476) - change: Add back policyDebug option (LavaMoat#440)


Follow-up to #475 spotted from going thru js example
nb: same RN v8 warnings (excluding Promises)
and in cli example console.error only on localhost:5000 (favicon.ico 404 only on refresh)
nb: js example
Should we mention in docs to expect these errors or are these unexpected to look at fixing?No console.error's running zero extensions