freesewing/sites/dev/next.config.mjs

import configBuilder from '../shared/config/next.mjs'
import i18nConfig from './next-i18next.config.js'
import { banner } from '../../scripts/banner.mjs'
import withBundleAnalyzer from '@next/bundle-analyzer'

let config = configBuilder({ site: 'dev' })
config.i18n = i18nConfig.i18n

// Say hi
console.log(banner + '\n')

config.eslint = {
  // Ignore linter for now
  ignoreDuringBuilds: true,
}

// To run the bundle analyzer, run:
// ANALYZE=true yarn build
if (process.env.ANALYZE) config = withBundleAnalyzer(config)(config)

export default config
chore: Adapt sites to recent changes 2022-06-17 12:02:09 +02:00			`import configBuilder from '../shared/config/next.mjs'`
feat(shared): Support for translation in Dot custom component 2022-05-20 15:34:08 +02:00			`import i18nConfig from './next-i18next.config.js'`
fix(dev): Fixed build issues after recent changes 2022-06-19 16:09:53 +02:00			`import { banner } from '../../scripts/banner.mjs'`
chore(dev): Re-folded all docs into one page, dropped viz.js Did some digging into why the page size had ballooned, and it turns out it was due to viz.js taking up half the bundle size. So I've dropped the Dot custom mdx component, and reverted to having all pages served from one page using getStaticPaths. Might optimize a bit more later, but for now page size first load JS went from 816KB to 272KB so that's a big improvement. 2022-10-03 00:14:11 +02:00			`import withBundleAnalyzer from '@next/bundle-analyzer'`
feat(fs.dev) Setup next 12 & mdx 2 with ESM 2021-12-10 09:56:19 +01:00
feat(dev): Ported dev site to new v3 site framework 2023-05-16 10:34:13 +02:00			`let config = configBuilder({ site: 'dev' })`
feat(shared): Support for translation in Dot custom component 2022-05-20 15:34:08 +02:00			`config.i18n = i18nConfig.i18n`
chore: Fixing linter warnings 2022-07-12 20:09:17 +02:00
			`// Say hi`
chore(dev): Guard bundle analyzer behind env var 2022-10-03 17:49:40 +02:00			`console.log(banner + '\n')`
feat(dev): Added next-i18next to dev site 2022-02-13 16:00:00 +01:00
chore(dev): Re-folded all docs into one page, dropped viz.js Did some digging into why the page size had ballooned, and it turns out it was due to viz.js taking up half the bundle size. So I've dropped the Dot custom mdx component, and reverted to having all pages served from one page using getStaticPaths. Might optimize a bit more later, but for now page size first load JS went from 816KB to 272KB so that's a big improvement. 2022-10-03 00:14:11 +02:00			`config.eslint = {`
			`// Ignore linter for now`
chore(dev): Guard bundle analyzer behind env var 2022-10-03 17:49:40 +02:00			`ignoreDuringBuilds: true,`
chore(dev): Re-folded all docs into one page, dropped viz.js Did some digging into why the page size had ballooned, and it turns out it was due to viz.js taking up half the bundle size. So I've dropped the Dot custom mdx component, and reverted to having all pages served from one page using getStaticPaths. Might optimize a bit more later, but for now page size first load JS went from 816KB to 272KB so that's a big improvement. 2022-10-03 00:14:11 +02:00			`}`
chore: Supress webpack warnings about named imports from JSON This suppresses a warning in webpack v5 when importing the version from the package.json file like a named export. This use to be fine in webpack v4 but in v5 it's deprecated to be more inline with the way it works in NodeJS. That being said, it's very usefull as there's no need to pull in the entire package.json file. Futhermore, esbuild supports this out of the box so we also use it in our build scripts. So for now I'm supressing this warning. In FreeSewing v3 we'll re-evaluate this. 2022-06-12 22:37:04 +02:00
chore(dev): Guard bundle analyzer behind env var 2022-10-03 17:49:40 +02:00			`// To run the bundle analyzer, run:`
			`// ANALYZE=true yarn build`
			`if (process.env.ANALYZE) config = withBundleAnalyzer(config)(config)`
chore: Supress webpack warnings about named imports from JSON This suppresses a warning in webpack v5 when importing the version from the package.json file like a named export. This use to be fine in webpack v4 but in v5 it's deprecated to be more inline with the way it works in NodeJS. That being said, it's very usefull as there's no need to pull in the entire package.json file. Futhermore, esbuild supports this out of the box so we also use it in our build scripts. So for now I'm supressing this warning. In FreeSewing v3 we'll re-evaluate this. 2022-06-12 22:37:04 +02:00
feat(dev): Added next-i18next to dev site 2022-02-13 16:00:00 +01:00			`export default config`