Amos Yuen

So how should we move forward with this?

After poking through the code, there seems to be two problems in v3. In the examples cited I am using these options for module resolver: ```js { root: ['.'], extensions:...

I created PR https://github.com/tleunen/babel-plugin-module-resolver/pull/247 to address those two issues. I set stripExtensions by default to the extensions param to preserve the old behavior of stripping extensions specified.

Yep, that's correct that I need to keep the `.web.js` function. Thanks for explaining, makes more sense now as why it works the way it does. While it might be...

For issue https://github.com/tleunen/babel-plugin-module-resolver/issues/201 I've created a PR https://github.com/tleunen/babel-plugin-module-resolver/pull/247 for adding a `stripExtensions` option that does something similar to what the OP wants.

same problem, mrmaxon's workaround works for me

From inspecting the snooze json payload returned from the HTTP API, for cameras it looks fairly simple: ```json { "account_id": "", // Not sure how this is used if used...

I'm curious why it does a nested query for something that could easily be done without the nested query. As far as I can tell there are two things that...

Created https://github.com/stems/join-monster/pull/324 to address this

@yury did you ever figure this out?