Sam Broner

After some review, I think require is the easiest way to solve this for me. However, I did find this caveat on the EJS readme I missed before: https://github.com/mde/ejs#caveats I...

I also have this issue, I can resolve it by setting ```var query = {};``` My loader rule is below. ``` { test: /\.ejs$/, use: { loader: 'ejs-compiled-loader', options: {...

@beeryukov, I believe I resolved this for myself. I was using the HtmlWebpackPlugin like this: ``` new HtmlWebpackPlugin({ template: "!!ejs-compiled-loader!./public/index.ejs", templateParameters: { posts: postTemplates, post: false } }), ``` However,...

Fair. I do encourage you to play around with the functions code. You may find discovery much easier. I'm finding myself evangelizing TypeScript, especially when helping devs who are coming...

I will add that I prefer the discoverability in the current model. A dev really "gets right into it" in with the existing infra. The issue is (IMO) that a...

Happy to help as well (On the Fluid team at Microsoft.) I talked to @captainsafia about this and I think she's chatted with @saulshanabrook a while back about Fluid. You...

1. Good feedback. The OSS libraries have no M365 requirements. 2. All of the code needed to run the service is in the repo. We also published some [images to...

Excellent link to benchmark. Thank you. > Do you mean the GQL client would convert/resolve the request and transport it via the Fluid wire protocol, and then the server would...

Hopefully that package works as a drop in replacement, we may be short on nested list support. Happy to talk about it!

@artf would you support moving to typescript? I'm interested in this upgrade and can help, but I'd rather go from .js -> .ts than make .dts files. A little perspective,...