-
I have an existing project that has a top level The only way I can get around this right now is to put fomantic-ui in a separate project and not controlled by the same npm. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
It seems like it’s my fault. I’ve changed the base path in Before: {
"base": "./",
"paths": {
"source": {
"config": "semantic/src/theme.config",
"definitions": "semantic/src/definitions/",
"site": "semantic/src/site/",
"themes": "semantic/src/themes/"
},
"output": {
"packaged": "public/static/dist/",
"uncompressed": "public/static/dist/components/",
"compressed": "public/static/dist/components/",
"themes": "public/static/dist/themes/"
},
"clean": "public/static/dist/"
},
"permission": false,
"autoInstall": false,
"rtl": false,
"version": "2.8.7",
"admin": false
} After: {
"base": "semantic/",
"paths": {
"source": {
"config": "src/theme.config",
"definitions": "src/definitions/",
"site": "src/site/",
"themes": "src/themes/"
},
"output": {
"packaged": "../public/static/dist/",
"uncompressed": "../public/static/dist/components/",
"compressed": "../public/static/dist/components/",
"themes": "../public/static/dist/themes/"
},
"clean": "../public/static/dist/"
},
"permission": false,
"autoInstall": false,
"rtl": false,
"version": "2.8.7",
"admin": false
} |
Beta Was this translation helpful? Give feedback.
It seems like it’s my fault. I’ve changed the base path in
semantic.json
in order for it to put thedist
in a different folder. Changing the base back tosemantic/
solved the issue.Before: