|
1 mese fa | |
---|---|---|
.. | ||
src | 4c8279172c chore: remove @type/next temporarily to avoid node 18 problem | 1 anno fa |
README.md | 626c4b9f9e Feat/support next (#245) | 3 anni fa |
package.json | 0c83570b17 v2.87.0-beta.0 | 1 mese fa |
tsconfig.json | a0a3687d00 feat: formApi add scrollToError (#2294) | 1 anno fa |
A Next.js extension for Semi Design.
Because Next.js does not support the global introduction of css in third-party code, but semi does. In order to support Next.js, it is necessary to exclude the css reference in the semi code at compile time.
Install @douyinfe/semi-next
as a development dependency:
npm install --save-dev @douyinfe/semi-next
# or
yarn add --dev @douyinfe/semi-next
Create a next.config.js
in your project.
// next.config.js
const semi = require('@douyinfe/semi-next').default({/* the extension options */});
module.exports = semi({
// your custom Next.js configuration
});
Type: Boolean
Default: true
In the compilation phase, whether to exclude css references.Used to solve the problem that Next.js does not support the global introduction of css in third-party code.See this discussion.