[
https://issues.apache.org/jira/browse/CAMEL-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147113#comment-17147113
]
David Jencks commented on CAMEL-15249:
--------------------------------------
I wasn't intending to suggest that we use npm, just that I could get this
working with npm and not with yarn. I assume someone more familiar with yarn
could get it working with yarn.
However, I'm coming to the conclusion that perhaps a yarn workspace is a good
idea, since it's possible to depend on a UI bundle and access it through
require. This would make the antora build explicitly depend on the UI bundle
in package.json.
> Utilize yarn workspaces
> -----------------------
>
> Key: CAMEL-15249
> URL: https://issues.apache.org/jira/browse/CAMEL-15249
> Project: Camel
> Issue Type: Improvement
> Components: website
> Reporter: Zoran Regvart
> Priority: Major
>
> To make the build simpler, i.e. that we just need to run {{yarn}} followed by
> {{yarn build}} we can utilize [Yarn
> workspaces|https://classic.yarnpkg.com/en/docs/workspaces/]. By using
> workspaces we would not need to change into {{antora-ui-camel}} and build
> there, but the Antora UI would be built as a dependency/module of the
> workspace.
> Perhaps we can even make it so that we only need to run {{yarn}} (not so sure
> this is a good idea) or we only need to run {{yarn build}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
