rsnext/examples/with-reasonml-todo/package.json

{
  "name": "with-reasonml-todo",
  "version": "1.0.0",
  "scripts": {
    "dev": "concurrently \"bsb -clean-world -make-world -w\" \"next dev\"",
    "dev:reason": "bsb -clean-world -make-world -w",
    "dev:next": "next dev",
    "build": "bsb -clean-world -make-world && next build",
    "start": "next start"
  },
  "license": "MIT",
  "dependencies": {
    "next": "latest",
    "next-transpile-modules": "^7.3.0",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "reason-react": "^0.7.0"
  },
  "devDependencies": {
    "@babel/core": "^7.4.3",
    "bs-platform": "7.2.2",
    "concurrently": "^4.1.0"
  }
}
New Example: with-reasonml-todo(#7346) 2019-05-23 23:48:13 +02:00			`{`
chore: update example names to match their folders (#16268) What's the problem this PR addresses? A decent amount of the examples don't have a `name` field in `package.json` that matches their folder name, meaning they either lack a name or the names are duplicated. I was testing Yarn 2 workspaces using the entire examples directory and needed to get rid of the duplicates. How did you fix it? Updated the names to match the names of their folders 2020-09-05 23:23:51 +02:00			`"name": "with-reasonml-todo",`
New Example: with-reasonml-todo(#7346) 2019-05-23 23:48:13 +02:00			`"version": "1.0.0",`
			`"scripts": {`
			`"dev": "concurrently \"bsb -clean-world -make-world -w\" \"next dev\"",`
			`"dev:reason": "bsb -clean-world -make-world -w",`
			`"dev:next": "next dev",`
			`"build": "bsb -clean-world -make-world && next build",`
			`"start": "next start"`
			`},`
Ensure all examples are MIT licensed (#16691) 2020-08-30 04:32:35 +02:00			`"license": "MIT",`
New Example: with-reasonml-todo(#7346) 2019-05-23 23:48:13 +02:00			`"dependencies": {`
			`"next": "latest",`
Update next-transpile-modules to 7.3.0 across examples (#26040) ## Documentation / Examples - [x] Make sure the linting passes Just updated `next-transpile-modules` across examples. We shipped a workaround in 7.2 for the one breaking change that scared people from updating from v4 to v5+, I tested the updated examples, so we should be good. 2021-06-13 18:21:38 +02:00			`"next-transpile-modules": "^7.3.0",`
Update examples to use React 17 (#26133) [With next 11 requiring react 17](https://nextjs.org/blog/next-11#upgrade-guide), most of the examples need to be updated, so the following snippet updated all the examples to a compatible react version. ```bash cd examples/ fd -g 'package.json' \| xargs sed -r -i 's/"react": "."/"react": "^17.0.2"/ fd -g 'package.json' \| xargs sed -r -i 's/"react-dom": "."/"react-dom": "^17.0.2"/' # exclude experimental react version git checkout with-reason-relay/package.json ``` 2021-06-16 18:43:26 +02:00			`"react": "^17.0.2",`
			`"react-dom": "^17.0.2",`
New Example: with-reasonml-todo(#7346) 2019-05-23 23:48:13 +02:00			`"reason-react": "^0.7.0"`
			`},`
			`"devDependencies": {`
			`"@babel/core": "^7.4.3",`
A little bit of maintenance on the ReasonML examples (#11662) * Add babel-types package `next dev` was failing with: ``` Error: Cannot find module 'babel-types' ``` * Upgrade to the latest bs-platform Also add the `babel-types` package to stop the `next dev` command from complaining. * Remove extraneous babel-plugin-bucklescript dependency. Seems the dependency has been deprecated, and it doesn't seem to be required anyways. 2020-04-06 10:44:01 +02:00			`"bs-platform": "7.2.2",`
New Example: with-reasonml-todo(#7346) 2019-05-23 23:48:13 +02:00			`"concurrently": "^4.1.0"`
			`}`
			`}`