* Add missing CSS loaders for todomvc app
Currently webpack does not bundle the index.css file located in the root
directory. This PR adds the corresponding plugins and loaders to ensure
the file is correctly bundled.
Fixes#3443
* Fixed failing CI build
Bumped version of `css-loader` as we're on webpack 5 already.
Signed-off-by: Oliver T <geronimooliver00@gmail.com>
---------
Signed-off-by: Oliver T <geronimooliver00@gmail.com>
* add `#![no_implicit_prelude]` to `test-macro/ui-tests`
* prefix `Some` and `None` with `::core::option::Option`
* fix `test-macro/ui-tests/should_panic.stderr` line numbers
---------
Co-authored-by: Harry Barber <harrybarber@protonmail.com>
I noticed that none of the examples that compile using `wasm-pack` were working properly in https://rustwasm.github.io/wasm-bindgen/exbuild. I think this is happening because `wasm-pack` generates a `.gitignore` for the `pkg` folder, which the GitHub Pages uploader is interpreting to mean 'don't upload this'.
This PR makes CI delete those `.gitignore`s to try and fix that. It's still a draft because I don't know if it's actually going to work.
This isn't _that_ severe, since the only broken example which is actually linked to from the guide is the WebSockets example. Once I've seen whether this has worked I might go ahead and add links for the rest of the `wasm-pack`-built examples as well.
There were several pages that had been added to the guide, but were inaccessible due to not being listed in `SUMMARY.md` (which is how you specify the layout for the left sidebar). This PR fixes that.
I also noticed that there were two pages for the same `typscript_type` attribute: one in the 'on JS imports' section (which was inaccessible) and one in the 'on Rust exports' section. These aren't for two different versions of the attribute; they're both for the same attribute which can only be applied to JS imports.
The one in the 'on JS imports' section was much less detailed, so I got rid of it and moved the other one into its place.
Closes#2426 (an issue that was opened ages ago about the `typescript_type` page being in the wrong section). There was a bit of discussion there about whether it does actually belong in the 'on Rust exports' section, since despite being directly applied to JS imports its usage is to change the TypeScript output for Rust exports, but I think that the site where it's applied is more important.
