rsnext/examples/with-semantic-ui/package.json

{
  "private": true,
  "scripts": {
    "dev": "next",
    "build": "next build",
    "start": "next start"
  },
  "dependencies": {
    "next": "latest",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "semantic-ui-css": "^2.4.1",
    "semantic-ui-react": "^2.0.4"
  }
}
Add/semantic ui example (#1753) * Using developit/unfetch as the Fetch API polyfill * Added Semantic UI React example * Fixed linting issues 2017-04-22 14:54:35 +02:00			`{`
Clean up examples `package.json` (#27121) Clean up package.json files in the `examples` directory: - Add `private: true` - Remove `version` (because they are irrelevant for packages that are not meant to be published) - Remove `name` (because they are optional for packages that are not meant to be published, and when someone clones an example, they often rename it and the property becomes stale) - Remove `author` - Remove `description` - Remove `license` Also remove `with-dynamic-app-layout` example completely, since it does the same as `layout-component` (https://github.com/vercel/next.js/pull/27121#discussion_r668178408). ## Documentation / Examples - [x] Make sure the linting passes 2021-07-12 21:58:03 +02:00			`"private": true,`
Add/semantic ui example (#1753) * Using developit/unfetch as the Fetch API polyfill * Added Semantic UI React example * Fixed linting issues 2017-04-22 14:54:35 +02:00			`"scripts": {`
			`"dev": "next",`
Clean up examples directory (#11169) * Remove outdated examples * Remove outdated example * Remove outdated example that doesn't show best practices * Remove outdated example * Remove outdated example * Remove outdated example * Update preact example * Update using-router to use useRouter * Remove outdated example * Remove outdated example * Remove outdated example * Remove outdated example * Remove outdated example * Remove outdated example * Combine examples * Simplify offered examples * Remove outdated example * Add link to new example * Removed outdated example * Markdown example has been improved * Remove example that showed bad practices * Remove outdated example * Update polyfills example * Remove outdated example * Remove outdated example * Remove outdated example * Removed outdated example * Remove outdated example * Remove outdated example * Remove outdated example * Remove outdated example * Update webassembly example * Move example 2020-03-18 13:45:31 +01:00			`"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 14:54:35 +02:00			`"start": "next start"`
			`},`
			`"dependencies": {`
fix(examples): bring `with-semantic-ui` example up-to-date (#32805) 2021-12-25 00:07:30 +01:00			`"next": "latest",`
Update Examples to use React 18 (#42027) This PR updates the minimum version of React used by examples from 17.0.2 to 18.2.0. Fixes #41975 ## Bug - [x] Related issues linked using `fixes #41975` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see `contributing.md` ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm build && pnpm lint` - [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) 2022-10-28 19:43:20 +02:00			`"react": "^18.2.0",`
			`"react-dom": "^18.2.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 08:37:24 +01:00			`"semantic-ui-css": "^2.4.1",`
fix(examples): bring `with-semantic-ui` example up-to-date (#32805) 2021-12-25 00:07:30 +01:00			`"semantic-ui-react": "^2.0.4"`
Remove `licence` from all `example/package.json` that has them (#28007) * Add licences to all example/package.json that lack them * Revert "Add licences to all example/package.json that lack them" This reverts commit 5d4e25012f7334772b8ef5924bc355277e827cba. * Update check-examples to remove `license` field from examples * Remove `license` from all examples. This was mentioned in vercel/next.js#27121 but it looks like it didn't end up being in the merge? Co-authored-by: JJ Kasper <jj@jjsweb.site> 2021-08-14 17:48:39 +02:00			`}`
Add/semantic ui example (#1753) * Using developit/unfetch as the Fetch API polyfill * Added Semantic UI React example * Fixed linting issues 2017-04-22 14:54:35 +02:00			`}`