terribleplan/next.js
1
0
Fork 0
mirror of https://github.com/terribleplan/next.js.git synced 2024-01-19 02:48:18 +00:00
Code Issues Releases Wiki Activity
next.js/examples/with-semantic-ui/package.json

24 lines
480 B
JSON
Raw Normal View History

Add/semantic ui example (#1753) * Using developit/unfetch as the Fetch API polyfill * Added Semantic UI React example * Fixed linting issues
2017-04-22 12:54:35 +00:00
{
"name": "with-semantic-ui",
"version": "1.0.0",
"scripts": {
"dev": "next",
Updates with-semantic-ui example (#6158) I tried to make the example a bit more descriptive. I changed `publicPath` in `now.config.js` to be `/_next/static/`, in place of `./`, and `outputPath` to `static/` in place of `static/css/`. The reason is that the webpack config will still fallback to `file-loader` for any content that is imported by the user and which is bigger that `8192` bytes. I think this content should not land in the css folder, which should probably stay css specific. Moreover, for user content, like regular images, the former settings will fail. If you have this: ```javascript import LargeFile from './LargeFile.png' ``` it would be placed in `static/css/` but its url would resolve to `<base-url>/LargeFile.png`, which will fail. It works for semantic-ui alone, because `@zeit/next-css` will put the styles in `static/css/` and so `publicPath` of `./` would work just fine. Putting assets in `static/` and setting `publicPath` to '/_next/static/' will resolve correctly for both semantic-ui related assets as well as for regular user assets. I hope I am not mixing something up. I tested it locally and in serverless deployment, and this looks pretty consistent.
2019-01-28 07:37:24 +00:00
"now-build": "next build",
Add/semantic ui example (#1753) * Using developit/unfetch as the Fetch API polyfill * Added Semantic UI React example * Fixed linting issues
2017-04-22 12:54:35 +00:00
"start": "next start"
},
"dependencies": {
Updates with-semantic-ui example (#6158) I tried to make the example a bit more descriptive. I changed `publicPath` in `now.config.js` to be `/_next/static/`, in place of `./`, and `outputPath` to `static/` in place of `static/css/`. The reason is that the webpack config will still fallback to `file-loader` for any content that is imported by the user and which is bigger that `8192` bytes. I think this content should not land in the css folder, which should probably stay css specific. Moreover, for user content, like regular images, the former settings will fail. If you have this: ```javascript import LargeFile from './LargeFile.png' ``` it would be placed in `static/css/` but its url would resolve to `<base-url>/LargeFile.png`, which will fail. It works for semantic-ui alone, because `@zeit/next-css` will put the styles in `static/css/` and so `publicPath` of `./` would work just fine. Putting assets in `static/` and setting `publicPath` to '/_next/static/' will resolve correctly for both semantic-ui related assets as well as for regular user assets. I hope I am not mixing something up. I tested it locally and in serverless deployment, and this looks pretty consistent.
2019-01-28 07:37:24 +00:00
"next": "canary",
Test updater script on examples folder (#5993) I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.: ``` $ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0" ``` This PR contains the result against the examples folder.
2019-01-05 11:19:27 +00:00
"react": "^16.7.0",
"react-dom": "^16.7.0",
Updates with-semantic-ui example (#6158) I tried to make the example a bit more descriptive. I changed `publicPath` in `now.config.js` to be `/_next/static/`, in place of `./`, and `outputPath` to `static/` in place of `static/css/`. The reason is that the webpack config will still fallback to `file-loader` for any content that is imported by the user and which is bigger that `8192` bytes. I think this content should not land in the css folder, which should probably stay css specific. Moreover, for user content, like regular images, the former settings will fail. If you have this: ```javascript import LargeFile from './LargeFile.png' ``` it would be placed in `static/css/` but its url would resolve to `<base-url>/LargeFile.png`, which will fail. It works for semantic-ui alone, because `@zeit/next-css` will put the styles in `static/css/` and so `publicPath` of `./` would work just fine. Putting assets in `static/` and setting `publicPath` to '/_next/static/' will resolve correctly for both semantic-ui related assets as well as for regular user assets. I hope I am not mixing something up. I tested it locally and in serverless deployment, and this looks pretty consistent.
2019-01-28 07:37:24 +00:00
"semantic-ui-css": "^2.4.1",
"semantic-ui-react": "^0.84.0"
},
"devDependencies": {
"@zeit/next-css": "^1.0.1",
"file-loader": "^3.0.1",
"url-loader": "^1.1.2",
"webpack": "^4.29.0"
Add/semantic ui example (#1753) * Using developit/unfetch as the Fetch API polyfill * Added Semantic UI React example * Fixed linting issues
2017-04-22 12:54:35 +00:00
},
"license": "ISC"
}
Reference in a new issue Copy permalink