Thomas L

Results 1 comments of Thomas L

For me, #381 is more the next.js way to fix it.