Soviut

I had a similar issue with my function on Netlify where I needed to make sure `chrome-aws-lambda` as an external module. netlify.toml ```toml [functions.render] external_node_modules = ["chrome-aws-lambda"] ``` Perhaps you...

You can use the `image` attribute like this. ``` api_stub: image: clue/json-server volumes: - ./api.json:/data/db.json ports: - '1337:80' ``` (Note that I'm intentionally mapping a really obvious external port `1337`)

For the time being, I've worked around this by changing my build script in `package.json` from this ```json "build": "vue-tsc --noEmit && vite build", ``` to this ```json "build": "vite...

In both versions it's giving an error because you don't have a `build` script defined in your `package.json`. If you don't have a `build` script, don't run the `npm run...

+1 for this

The license is also listed in the composer.json file but @hopeseekr why not do a pull request with a license file setup?

All package/dependency managers must include the license, but I agree that someone should add the license file. Could you do a pull request? On Monday, August 17, 2015, Theodore R....

Using a `watch` with `immediate: true` is what worked for me. `immediate` guarantees the handler will run on setup as well as when `result` changes. ```javascript const { result }...

@Murderlon It doesn't look like it. I'm referring to the Vue component specifically. They do not `emit` events. I have done the following in my wrapper (note that I'm using...

yes, the options API is still fully supported in Vue 3 so `this.$emit` is safe to use. Somewhat tangential to this, I think how Uppy handles events internally could be...