Monorepo
#6450
Replies: 2 comments
-
This sounds useful - "traits can be their own package @terriajs/traits (so we can use them in the backend without entire terriajs)" |
Beta Was this translation helpful? Give feedback.
0 replies
-
Breaking down terriajs into parts may be useful, but I think it is less important than making terriajs a proper library (builds to js, typings & assets and can be imported into e.g. TerriaMap, rather than only building as part of TerriaMap) and having a proper plugin interface. terriajs should be usable in the backend as is. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Thinking about this a lot lately and would like to hear the TerriaJS team opinion on it. What do you think about switching terriajs to the monorepo (in v9/v10 or even later), i.e. traits can be their own package
@terriajs/traits
(so we can use them in the backend without entire terriajs), catalog items can also be extracted as proposed in #6227Beta Was this translation helpful? Give feedback.
All reactions