C. T. Lin

I found that this is not working: ```js this.forge(extend({}, filter)).fetchAll(options); ``` (got select command with no where condition) But this works: ```js const model = this.forge(); return model.where(model.format(extend({}, filter))).fetchAll(options) ```...

This implement might be wrong, but how can we avoid timestamp comparing failed because of precision issue?

We should implement same logic in bookshelf model destroy: ```js if (syncing.id != null) query.where(syncing.format({[syncing.idAttribute]: syncing.id})); if (_.filter(query._statements, {grouping: 'where'}).length === 0) { throw new Error('A model cannot be destroyed...

Next.js adds fallbacks for node built-in modules by using `resolve.fallback`: https://github.com/vercel/next.js/blob/384953b35c5e9935bb4a2fcdfe5056efb73cd740/packages/next/build/webpack-config.ts#L628-L659 And this feature now doesn't support node protocol: https://github.com/webpack/webpack/issues/14166

@probablyup @kitten Is there any chance to reconsider providing `styled` as a named export (#3437 #3438)? This issue definitely blocks the adoption of using styled-components with [Next.js 12 Native ES...

I think we should not include web stuff into this boilerplate, it will increase unnecessary complexity in a desktop-only application. But if someone is interested in how to build them...

@doulmi I'd recommend for using [nativefier](https://github.com/jiahaog/nativefier) to create a new web app runs on both env. It's the simplest way that I could ever find.

@TimothyLe Please be watchful with the wording. In such a OSS project, no one owes you anything.

Hi @pepper, this definitely an important use case that we want to support in Bottender. We were all set to support this use case by using `destination` field from LINE...

Hi @pepper, We have implemented a solution in `v1.5.0-alpha.3` using a `getConfig` function: ```js module.exports = { channels: { line: { enabled: true, path: '/webhooks/line/:channelId', async getConfig({ params }) {...