|
3 gadi atpakaļ | |
---|---|---|
.. | ||
src | 1d87b98bee fix: alias not work after config semi-next in next.js project, close #630 (#658) | 3 gadi atpakaļ |
README.md | 626c4b9f9e Feat/support next (#245) | 3 gadi atpakaļ |
package.json | e4926d98b1 v2.19.0-alpha.7 | 3 gadi atpakaļ |
tsconfig.json | 626c4b9f9e Feat/support next (#245) | 3 gadi atpakaļ |
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.