Skip to content
This repository was archived by the owner on Jul 9, 2025. It is now read-only.

[WIP] add expression parser to server dependencies#1440

Closed
a-b-r-o-w-n wants to merge 3 commits intomicrosoft:masterfrom
a-b-r-o-w-n:add-expression-parser
Closed

[WIP] add expression parser to server dependencies#1440
a-b-r-o-w-n wants to merge 3 commits intomicrosoft:masterfrom
a-b-r-o-w-n:add-expression-parser

Conversation

@a-b-r-o-w-n
Copy link
Contributor

@a-b-r-o-w-n a-b-r-o-w-n commented Oct 31, 2019

@hailiu2586 identified a few other packages that need to be added:

  • botbuilder-lg
  • ludown
  • lubuild

@a-b-r-o-w-n a-b-r-o-w-n changed the base branch from stable to master October 31, 2019 23:08
@a-b-r-o-w-n a-b-r-o-w-n changed the title add expression parser to server dependencies [WIP] add expression parser to server dependencies Oct 31, 2019
@boydc2014
Copy link
Contributor

@lei9444 can you help complete this, you know best about the exact version. this is abs related, for some reasons, yarn package resolution seems to not working. I think it's because the expression parser is published in myget. anyway, let's add them for now.

@boydc2014
Copy link
Contributor

boydc2014 commented Nov 1, 2019

em ... this is weird , lubuild is already there, in server/package.json and server never used botbuilder-lg nor botbuilder-expression-parser nor ludown, it's lib/indexers who depends on that. Not sure why those are identified those are missing packages. @hailiu2586 can you share the bundling process you used, so we can test and verify the fix? maybe create an issue with the description of expected behavior.

I suspect it might related to those packages are referred directly through url, instead of just version + config in npmrc. So @lei9444 you can create a PR which totally remove the use of absolute url in favor of the config in npmrc. We probably should rename all those with a @bfcomposer prefix.

I think that would largely fix the issue and keep us clean, at the same time Leilei you can talk to Hai about this if any special treatment need to be done here.

@boydc2014
Copy link
Contributor

em ... this is weird , lubuild is already there, in server/package.json and server never used botbuilder-lg nor botbuilder-expression-parser nor ludown, it's lib/indexers who depends on that. Not sure why those are identified those are missing packages. @hailiu2586 can you share the bundling process you used, so we can test and verify the fix? maybe create an issue with the description of expected behavior.

I suspect it might related to those packages are referred directly through url, instead of just version + config in npmrc. So @lei9444 you can create a PR which totally remove the use of absolute url in favor of the config in npmrc. We probably should rename all those with a @bfcomposer prefix.

I think that would largely fix the issue and keep us clean, at the same time Leilei you can talk to Hai about this if any special treatment need to be done here.

I think i understand the problem, actually it's the same problem of our docker build.

  • We want a bundled server or at least minimal server after we bundled client.
    We support that previously, but that's broken after we make server depends on "lib/shared" and "lib/indexers".

Before that, our server can install fully self-contained, in the docker build, i even created a clean layer for server to run yarn install separately.

# use a multi-stage build to reduce the final image size
FROM node:10-alpine
WORKDIR /app/Composer/server
COPY --from=build /src/Composer/packages/server .
RUN yarn --production && yarn cache clean

So, the packages Hai identified are the dependencies of 'lib/shared' and 'lib/indexers', perhaps @hailiu2586 already copied those two packages it self directly into server.

Anyway, we should fix this by give server a way to properly bundle itself, or at least bring the dependencies into server folder easily.

So not related to absolute url, it's a bundle issue we need to solve for abs-h and for our docker.

@boydc2014
Copy link
Contributor

I guess this is no longer needed? as long as abs-h followed the steps in our Dockerfile?

@a-b-r-o-w-n
Copy link
Contributor Author

a-b-r-o-w-n commented Nov 2, 2019 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants