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
chore: mergeback next -> identity-provider/2021-01-04 #216
chore: mergeback next -> identity-provider/2021-01-04 #216
Conversation
For now we just re-parse it in BigNumber.
This is a split from #132.
This includes a change to request_id from the identity-provider PR (#132) that I thought was related to something else, but is essential here with the new lerna packages. This moves the CI to using lerna entirely, and prevents running npm install (instead telling the user to run npx lerna bootstrap).
(Donno if we want |
I am skeptical of the |
The npm |
Dont' waste too much time on this. In 132 you never built the websites using lerna, so using a |
Sounds like you're referring to
|
…ys know how to deal with lockfileVersion 2
…s own package-lock.json
My skepticism was incorrect! Still feels odd to not have at least a major semver range in there (which I thought worked, but if this works too idc) |
"packages/authentication" | ||
"packages/authentication", | ||
"packages/bootstrap", | ||
"e2e/*" |
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.
Notably this does not include other packages/*
.
- Those can be added after this merge, which is still a valid mergeback (and then some!) of next -> feat(identity-provider): Identity Provider v1 #132
next
currently only hasidentity-provider
on top of the ones explicitly enumerated here, and idp is brand new code we should be thrilled to just iterate on top of once feat(identity-provider): Identity Provider v1 #132 is merged
"@typescript-eslint/parser", | ||
"eslint", | ||
"eslint-plugin-jsdoc", | ||
"typescript" |
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.
These hoist devDependencies that lerna doesn't even try to install (lerna devs consider devDeps it out of scope), but that e.g. lerna run lint
-> subpackage npm run lint
will expect to be around, e.g. eslint
.
Once this is merged, agent-js-devtools package can maybe completely go away?
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.
it shoudln't be in next anymore.
…/agent-js into bengo/1613514044/132-mergeback-1
Trying ways of landing #208
Why?