wasm-bindgen/examples/fetch/package.json

{
  "scripts": {
    "build": "webpack",
    "serve": "webpack-dev-server"
  },
  "devDependencies": {
    "@wasm-tool/wasm-pack-plugin": "0.2.1",
    "text-encoding": "^0.7.0",
    "html-webpack-plugin": "^3.2.0",
    "webpack": "^4.29.4",
    "webpack-cli": "^3.1.1",
    "webpack-dev-server": "^3.1.0"
  }
}
Initial example for the Fetch API 2018-08-18 17:20:42 -04:00			`{`
			`"scripts": {`
Fix polyfill of `TextEncoder` and `TextDecoder` This commit does a few things, including: * Fixing the generated JS of `wasm-bindgen` to allow polyfills to work. (a minor tweak of the generated JS) * All examples are updated to include a Webpack-specific polyfill for these two types to get examples working in Edge. * A new page has been added to the guide about supported browsers. This mentions known caveats like IE 11 requiring `wasm2js` as well as documenting some `TextEncoder` and `TextDecoder` workarounds for Edge. Closes #895 2018-09-28 20:01:46 -07:00			`"build": "webpack",`
Tweak package.json for `fetch` example 2018-09-17 17:38:07 -07:00			`"serve": "webpack-dev-server"`
Initial example for the Fetch API 2018-08-18 17:20:42 -04:00			`},`
			`"devDependencies": {`
Convert all examples to using wasm-pack This commit migrates all our examples to using `wasm-pack build` to compile their code and run `wasm-bindgen`. This should make it a bit easier to understand the examples as there's less to follow during the build step. Webpack projects are all using `@wasm-tool/wasm-pack-plugin` as well so the build step is simple `npm run serve`. Other examples which retain `build.sh` are just using `wasm-pack build` now 2019-01-08 15:14:15 -08:00			`"@wasm-tool/wasm-pack-plugin": "0.2.1",`
Fix polyfill of `TextEncoder` and `TextDecoder` This commit does a few things, including: * Fixing the generated JS of `wasm-bindgen` to allow polyfills to work. (a minor tweak of the generated JS) * All examples are updated to include a Webpack-specific polyfill for these two types to get examples working in Edge. * A new page has been added to the guide about supported browsers. This mentions known caveats like IE 11 requiring `wasm2js` as well as documenting some `TextEncoder` and `TextDecoder` workarounds for Edge. Closes #895 2018-09-28 20:01:46 -07:00			`"text-encoding": "^0.7.0",`
Examples: use html-webpack-plugin 2018-09-11 08:42:22 +03:00			`"html-webpack-plugin": "^3.2.0",`
chore: update pinned Webpack versions 2019-02-15 19:26:08 +01:00			`"webpack": "^4.29.4",`
update to "webpack-cli": "^3.1.1" 2018-09-25 18:50:27 -07:00			`"webpack-cli": "^3.1.1",`
Tweak package.json for `fetch` example 2018-09-17 17:38:07 -07:00			`"webpack-dev-server": "^3.1.0"`
Initial example for the Fetch API 2018-08-18 17:20:42 -04:00			`}`
			`}`