ashleygwilliams

• rubber plant - 1 pint/week bright afternoon sun
• ripple pepperomia - 1/2 cup/week, bringt indirect light
• pinstripe - 1 cup/week, morning/medium light
• prayer plant - 1/2 cup/week, bright morning sun
• pilea - 1/2 cup/week, bright indirect light
• bird's nest - 1 cup/week, cool, morning sun
• caleatha rose picta - 1 cup week summer/1/2 cup winter, bright morning sun
• sanseveria - 1/2-1 cup/week summer, 1 cup every 2 week, low is ok, bright for blooms

ashleygwilliams

- due today
  - KPIs - Ashley
  -Go to Market - Remy
  - Blogpost 1:2
    - Announcement
    - Open Source Docs
  - Engineering Update- Ashley
  - Trust and Safety Update - Rita
  -  UI Update -Rita
    - Promo Flash Message

ashleygwilliams

How the DevExp Team Works

.. actually surprisingly 2(ish) teams!

1. Docs/Template Gallery

• Victoria
• Kristian

2. Wrangler

• Ashley

ashleygwilliams

Minimal example making webpack and wasm/Emscripten work together.

Build instructions:

• Clone this gist
• npm install
• npm start
• Open http://localhost:8080
• Look at console

ashleygwilliams

index.js
package.json -> "name": "{{ project-name }}"
LICENSE
CODE_OF_CONDUCT
tests/
.gitignore
.prettier

ashleygwilliams

• ✨ Features

  • Non rustup environment support - [drager], pull/552

    Before now, wasm-pack had a hard requirement that rustup had to be in the PATH. While most Rust users userustup there are variety reasons to have an environment that doesn't use rustup. With this PR, we'll now support folks who are using a non-rustup environment!

  • Improved CLI Output - [alexcrichton], [pull/547]

ashleygwilliams

• ✨ Features

  • Add three build profiles and infrastructure for their toml config - [fitzgen], [issue/153] [issue/160] [pull/440]

    When originally conceived, wasm-pack was exclusively a packaging and publishing tool, which naively assumed that the crate author would simply run wasm-pack when they were ready to publish a wasm package. As a result, wasm-pack always ran cargo build in --release mode. Since then, wasm-pack has grown into an integrated build tool used at all stages of development, from idea conception to publishing, and as such has developed new needs.

In previous releases, we've supported a flag called --debug which will run cargo build in dev mode, which trades faster compilation speed for a lack of optimizations. We've renamed this flag to --dev to match cargo and added an additional flag, representing a third, intermediary, build profile, called --profiling which is useful for investigating performance issues. You can see all three flags and their use

ashleygwilliams

• So make it possible to add this feature, we need to add both async and await as keywords. But we also have to be careful that we’re not making old code invalid… code that might’ve used the words async or await as variable names. So we’re adding the keywords as part of Rust 2018. Even though the feature hasn’t landed yet, the keywords are now reserved.
• So make it possible to add this feature, Rust needs to add both async and await as keywords. But Rust also has to be careful that it's not making old code invalid… code that might’ve used the words async or await as variable names. So Rust is adding the keywords as part of Rust 2018. Even though the feature hasn’t landed yet, the keywords are now reserved.

--

• In our minds, it’s the second.
• For Rust, it's the second.

--

ashleygwilliams

{
  "dependencies": {
    "foo" : "1.0.0 - 2.9999.9999",
    "bar" : ">=1.0.2 <2.1.2",
    "baz" : ">1.0.2 <=2.3.4",
    "boo" : "2.0.1",
    "qux" : "<1.0.0 || >=2.3.1 <2.4.5 || >=2.5.2 <3.0.0",
    "asd" : "http://asdf.com/asdf.tar.gz"
  },
  "devDependencies": {

ashleygwilliams

[package]
#...

[dependencies]
#...

[npm]
moment = "~2.22" 
#sugar for moment = { version: "~2.22", type: prod }
mocha = { version: "mochajs/mocha#4727d357ea", type: dev }