wasm-bindgen/package.json

{
  "scripts": {
    "build": "webpack -p",
    "serve": "webpack-dev-server -p"
  },
  "devDependencies": {
    "@wasm-tool/wasm-pack-plugin": "0.2.3",
    "text-encoding": "^0.7.0",
    "html-webpack-plugin": "^3.2.0",
    "webpack": "^4.11.1",
    "webpack-cli": "^3.1.1",
    "webpack-dev-server": "^3.1.0"
  }
}
Don't run `npm install` during tests Instead add a `package.json` and use `yarn run`. 2018-03-02 14:20:05 -08:00			`{`
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			`"scripts": {`
			`"build": "webpack -p",`
			`"serve": "webpack-dev-server -p"`
			`},`
Don't run `npm install` during tests Instead add a `package.json` and use `yarn run`. 2018-03-02 14:20:05 -08:00			`"devDependencies": {`
Update @wasm-tool/wasm-pack-plugin requirement from 0.2.2 to 0.2.3 Updates the requirements on [@wasm-tool/wasm-pack-plugin](https://github.com/wasm-tool/wasm-pack-plugin) to permit the latest version. - [Release notes](https://github.com/wasm-tool/wasm-pack-plugin/releases) - [Commits](https://github.com/wasm-tool/wasm-pack-plugin/commits) Signed-off-by: dependabot[bot] <support@dependabot.com> 2019-01-31 08:12:51 +00:00			`"@wasm-tool/wasm-pack-plugin": "0.2.3",`
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",`
Another attempt to fix CI 2018-09-12 10:39:26 -07:00			`"html-webpack-plugin": "^3.2.0",`
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			`"webpack": "^4.11.1",`
update to "webpack-cli": "^3.1.1" 2018-09-25 18:50:27 -07:00			`"webpack-cli": "^3.1.1",`
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			`"webpack-dev-server": "^3.1.0"`
Don't run `npm install` during tests Instead add a `package.json` and use `yarn run`. 2018-03-02 14:20:05 -08:00			`}`
			`}`