af664d55df
Previously, we were using touch and mouse events to detect when we were in coarse/fine pointer mode. The problem with this is that many mobile devices emulate mouse events for backwards compatibility with websites not built for touch - so many touch events result in mouse events too. The solution to this is to use the unified pointer events API, and check the `pointerType` property to determine the device the user is using. This diff also contains some changes to make it so that multiplayer rooms "just work" over the LAN when devloping locally. ### Change Type - [x] `sdk` — Changes the tldraw SDK - [x] `bugfix` — Bug fix ### Release Notes - Fix a bug where coarse-pointer mode would get incorrectly detected on some touch devices
82 lines
2.8 KiB
TypeScript
82 lines
2.8 KiB
TypeScript
import react from '@vitejs/plugin-react-swc'
|
|
import { config } from 'dotenv'
|
|
import { defineConfig } from 'vite'
|
|
|
|
config({
|
|
path: './.env.local',
|
|
})
|
|
|
|
export const getMultiplayerServerURL = () => {
|
|
return process.env.MULTIPLAYER_SERVER?.replace(/^ws/, 'http')
|
|
}
|
|
|
|
function urlOrLocalFallback(mode: string, url: string | undefined, localFallbackPort: number) {
|
|
if (url) {
|
|
return JSON.stringify(url)
|
|
}
|
|
|
|
if (mode === 'development') {
|
|
// in dev, vite lets us inline javascript expressions - so we return a template string that
|
|
// will be evaluated on the client
|
|
return '`http://${location.hostname}:' + localFallbackPort + '`'
|
|
} else {
|
|
// in production, we have to fall back to a hardcoded value
|
|
return JSON.stringify(`http://localhost:${localFallbackPort}`)
|
|
}
|
|
}
|
|
|
|
// https://vitejs.dev/config/
|
|
export default defineConfig((env) => ({
|
|
plugins: [react({ tsDecorators: true })],
|
|
publicDir: './public',
|
|
build: {
|
|
// output source maps to .map files and include //sourceMappingURL comments in JavaScript files
|
|
// these get uploaded to Sentry and can be used for debugging
|
|
sourcemap: true,
|
|
|
|
// our svg icons break if we use data urls, so disable inline assets for now
|
|
assetsInlineLimit: 0,
|
|
},
|
|
// add backwards-compatible support for NEXT_PUBLIC_ env vars
|
|
define: {
|
|
...Object.fromEntries(
|
|
Object.entries(process.env)
|
|
.filter(([key]) => key.startsWith('NEXT_PUBLIC_'))
|
|
.map(([key, value]) => [`process.env.${key}`, JSON.stringify(value)])
|
|
),
|
|
'process.env.MULTIPLAYER_SERVER': urlOrLocalFallback(env.mode, getMultiplayerServerURL(), 8787),
|
|
'process.env.ASSET_UPLOAD': urlOrLocalFallback(env.mode, process.env.ASSET_UPLOAD, 8788),
|
|
'process.env.TLDRAW_ENV': JSON.stringify(process.env.TLDRAW_ENV ?? 'development'),
|
|
// Fall back to staging DSN for local develeopment, although you still need to
|
|
// modify the env check in 'sentry.client.config.ts' to get it reporting errors
|
|
'process.env.SENTRY_DSN': JSON.stringify(
|
|
process.env.SENTRY_DSN ??
|
|
'https://4adc43773d07854d8a60e119505182cc@o578706.ingest.sentry.io/4506178821881856'
|
|
),
|
|
},
|
|
server: {
|
|
proxy: {
|
|
'/api': {
|
|
target: getMultiplayerServerURL() || 'http://127.0.0.1:8787',
|
|
rewrite: (path) => path.replace(/^\/api/, ''),
|
|
ws: false, // we talk to the websocket directly via workers.dev
|
|
// Useful for debugging proxy issues
|
|
// configure: (proxy, _options) => {
|
|
// proxy.on('error', (err, _req, _res) => {
|
|
// console.log('[proxy] proxy error', err)
|
|
// })
|
|
// proxy.on('proxyReq', (proxyReq, req, _res) => {
|
|
// console.log('[proxy] Sending Request to the Target:', req.method, req.url)
|
|
// })
|
|
// proxy.on('proxyRes', (proxyRes, req, _res) => {
|
|
// console.log(
|
|
// '[proxy] Received Response from the Target:',
|
|
// proxyRes.statusCode,
|
|
// req.url
|
|
// )
|
|
// })
|
|
// },
|
|
},
|
|
},
|
|
},
|
|
}))
|