generated from finos/software-project-blueprint
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Dependencies Watchman #83
Labels
Studio Core Team
Opened by a member of the Studio core team
Type: Maintenance
DevOps, maintenance, admin works to do with the repository
Comments
We have upgraded |
3 tasks
Merged
This was referenced Sep 15, 2021
akphi
added
Type: Maintenance
DevOps, maintenance, admin works to do with the repository
and removed
Type: Discussion
labels
Nov 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Studio Core Team
Opened by a member of the Studio core team
Type: Maintenance
DevOps, maintenance, admin works to do with the repository
Dependency upgrades/bug-fixes to track
This list keeps track of dependencies that are either unstable or blockers to development in our project. Since unstable dependencies are usually marked with tag
@next
, or currently inalpha
,beta
channels, which can be ignored bydependabot
. For now, we want to have this pinned issue as the watchman, eventually, we should split it into smaller issuesbeta
version. Part ofwebpack@5
upgrade. (Resolved in Add support forDataSpace
#495)beta
version. Part ofwebpack@5
upgrade (Resolved in re-organization #422)babel@8
, a lot of configurations are to be set to default, we should keep track of these to slim down our babel preset.Jest
as test-runner #502Jest@27
will usejest-circus
by default so we don't need to manually specify this like right now.Jest@27
is currently being blocked due to@types/jest
not being upgraded. This is causing a weird error:The inferred type of ... cannot be named without a reference to 'jest/node_modules/pretty-format/build/types'
. Also, we should wait out a little bit as we need to confirmJest@27
works well withtesting-library
yarn workspaces foreach
quirk #501yarn workspaces foreach
does not support--skip-missing
flag, so if a workspace does not have a script with name specified, it will error out when we try to run such script on all workspaces (unlikelerna
). See [Feature]yarn workspaces foreach
features yarnpkg/berry#62typescript-eslint
lack of support forTypescript
project reference #500no-extraneous-dependencies
in [Fix]no-extraneous-dependencies
: add ESM intermediatepackage.json
support import-js/eslint-plugin-import#2121 to be published and enable that rulehusky@5
forces us to change our license. We have to wait till the early-access phase is over.Dependency features to try out
This list keeps track of nice dependency features that are already supported in the versions we have, but we haven't quite had the time and effort to apply.
yarn/berry: PnP is nice to try out but currently does not support ESM so we have to usenode_modules
as node linker mechanism. See 🎯 ESM Support for PnP yarnpkg/berry#638mobx: Use- this will be enforced and checked byoverride
forcomputed
properties where appropriate (i.e. when both super class and sub class have concretemethods/getters
)mobx
automatically. The last thing we need to do is to stop usingsuper.
in@computed
flow
annotation withmakeObservable
andflowResult
instead of wrapperflow(function * ...)
- Check out doctypescript@4.3
supports for theoverride
syntax. This is currently blocked byprettier
(Codebase cleanup and stabilize mapping editor #244)The text was updated successfully, but these errors were encountered: