esbuild | An extremely fast bundler for the web | Build Tool library

by evanw Go Version: 0.16.16 License: MIT

kandi X-RAY | esbuild Summary

esbuild is a Go library typically used in Utilities, Build Tool, Webpack applications. esbuild has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Website | Getting started | Documentation | Plugins | FAQ.

Support

Quality

Security

License

Reuse

kandi-support Support

esbuild has a medium active ecosystem.
It has 34512 star(s) with 962 fork(s). There are 300 watchers for this library.
There were 10 major release(s) in the last 6 months.
There are 249 open issues and 2266 have been closed. On average issues are closed in 11 days. There are 23 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of esbuild is 0.16.16

esbuild Support

Best in #Build Tool

Average in #Build Tool

esbuild Support

Best in #Build Tool

Average in #Build Tool

quality kandi Quality

esbuild has 0 bugs and 0 code smells.

esbuild Quality

Best in #Build Tool

Average in #Build Tool

esbuild Quality

Best in #Build Tool

Average in #Build Tool

security Security

esbuild has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
esbuild code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.

esbuild Security

Best in #Build Tool

Average in #Build Tool

esbuild Security

Best in #Build Tool

Average in #Build Tool

license License

esbuild is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.

esbuild License

Best in #Build Tool

Average in #Build Tool

esbuild License

Best in #Build Tool

Average in #Build Tool

build Reuse

esbuild releases are available to install and integrate.

esbuild Reuse

Best in #Build Tool

Average in #Build Tool

esbuild Reuse

Best in #Build Tool

Average in #Build Tool

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample Here

Get all kandi verified functions for this library.

esbuild Key Features

An extremely fast bundler for the web

esbuild Examples and Code Snippets

See all related Code Snippets

Community Discussions

Trending Discussions on esbuild

Serverless Offline & DynamoDB throws Local UnknownEndpoint: Inaccessible host: localhost at port 8000 Service may not be available in localhost region
How to access shadowDom when testing Lit element with open-wc
How to execute a npm/yarn script when testing a VSCode extension?
A way to load .wglsl files in Typescript files using esbuild?
Recommended way to use JSX with Vue3 + Vite
Angular ng build throws error write EPIPE
sveltekit or esbuild error: Two output files share the same path but have different contents
How do you export globals in a bundle with esbuild?
Rails 7 asset pipeline SassC::SyntaxError with Tailwind
error when deploying to Jenkins * from Css Minimizer version: "15.2-15.3"

Trending Discussions on esbuild

QUESTION

Serverless Offline & DynamoDB throws Local UnknownEndpoint: Inaccessible host: localhost at port 8000 Service may not be available in localhost region

Asked 2022-Apr-11 at 10:19

I'm playin around with Serverless and I have no luck getting serverless-offline to work with serverless-dynamodb-local. I have very minimal setup, it takes 3minutes to reproduce, I did it like this:

Generate a TS Serverless project like - sls create -t aws-nodejs-typescript --path folder-name
install dependencies npm i
Add DynamoDB local npm install --save serverless-dynamodb-local
Add serverless offline npm install serverless-offline --save-dev
Install dynamodb sls dynamodb install

Now I update serverless.ts file like

Include installed plugins in the correct order

  plugins: [
    'serverless-esbuild',
    'serverless-dynamodb-local',
    'serverless-offline'
  ],

In custom add DynamoDB config like

  custom: {
    esbuild: { ... },
    dynamodb: {
      stages: ['dev'],
      start: {
        migrate: true
      }
    }

Last step is to add DynamoDB in resources

  resources: {
    Resources: {
      usersTable: {
        Type: 'AWS::DynamoDB::Table',
        Properties: {
          TableName: 'firstTable',
          AttributeDefinitions: [{
            AttributeName: 'id',
            AttributeType: 'S',
          }],
          KeySchema: [{
            AttributeName: 'id',
            KeyType: 'HASH'
          }],
          ProvisionedThroughput: {
            ReadCapacityUnits: 1,
            WriteCapacityUnits: 1
          }
        }
      }
    }
  }

Now I try to spin it all up by running sls offline start -s dev and it throws error below (execution won't stop)
(this error is logically not thrown if I remove migrate: true from serverless.ts)

Dynamodb Local Started, Visit: http://localhost:8000/shell
UnknownEndpoint: Inaccessible host: `localhost' at port `8000'. This service may not be available in the `localhost' region.: DynamoDB - Error - 
Environment: darwin, node 17.3.1, framework 3.12.0 (local), plugin 6.2.1, SDK 4.3.2
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues

Error:
UnknownEndpoint: Inaccessible host: `localhost' at port `8000'. This service may not be available in the `localhost' region.
at Request.ENOTFOUND_ERROR (...node_modules/aws-sdk/lib/event_listeners.js:529:46)
at Request.callListeners (...node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (...node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (...node_modules/aws-sdk/lib/request.js:686:14)
at error (...node_modules/aws-sdk/lib/event_listeners.js:361:22)
at ClientRequest.<anonymous> (...node_modules/aws-sdk/lib/http/node.js:99:9)
at ClientRequest.emit (node:events:390:28)
at ClientRequest.emit (node:domain:475:12)
at Socket.socketErrorListener (node:_http_client:442:9)
at Socket.emit (node:events:390:28)
at Socket.emit (node:domain:475:12)
at emitErrorNT (node:internal/streams/destroy:164:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

Even though error is thrown, I'm still able to successfully execute

> aws dynamodb list-tables --endpoint-url http://localhost:8000 --region localhost
{
    "TableNames": []
}

I didn't change any other code than described above. I'd guess it will be something really basic, like I'm missing some config or something somewhere, but I can't find anything in docs or other posts that would help. Any ideas welcome.

...and since I know some version had troubles in the past here is package.json I'm running with

  "engines": {
    "node": ">=14.15.0"
  },
  "dependencies": {
    "@middy/core": "^2.5.3",
    "@middy/http-json-body-parser": "^2.5.3",
    "serverless-dynamodb-local": "^0.2.40"
  },
  "devDependencies": {
    "@serverless/typescript": "^3.0.0",
    "@types/aws-lambda": "^8.10.71",
    "@types/node": "^14.14.25",
    "esbuild": "^0.14.11",
    "json-schema-to-ts": "^1.5.0",
    "serverless": "^3.0.0",
    "serverless-esbuild": "^1.23.3",
    "serverless-offline": "^8.5.0",
    "ts-node": "^10.4.0",
    "tsconfig-paths": "^3.9.0",
    "typescript": "^4.1.3"
  },

here's full serverless.ts if it helps

const serverlessConfiguration: AWS = {
  service: 'aws-onboarding-api',
  frameworkVersion: '3',
  plugins: [
    'serverless-esbuild',
    'serverless-dynamodb-local',
    'serverless-offline'
  ],
  provider: {
    name: 'aws',
    runtime: 'nodejs14.x',
    apiGateway: {
      minimumCompressionSize: 1024,
      shouldStartNameWithService: true,
    },
    environment: {
      AWS_NODEJS_CONNECTION_REUSE_ENABLED: '1',
      NODE_OPTIONS: '--enable-source-maps --stack-trace-limit=1000',
    },
  },
  // import the function via paths
  functions: { hello },
  package: { individually: true },
  custom: {
      esbuild: {
      bundle: true,
      minify: false,
      sourcemap: true,
      exclude: ['aws-sdk'],
      target: 'node14',
      define: { 'require.resolve': undefined },
      platform: 'node',
      concurrency: 10,
    },
    dynamodb: {
      stages: ['dev'],
      start: {
        migrate: true
      }
    }
  },
  resources: {
    Resources: {
      usersTable: {
        Type: 'AWS::DynamoDB::Table',
        Properties: {
          TableName: 'firstTable',
          AttributeDefinitions: [{
            AttributeName: 'id',
            AttributeType: 'S',
          }],
          KeySchema: [{
            AttributeName: 'id',
            KeyType: 'HASH'
          }],
          ProvisionedThroughput: {
            ReadCapacityUnits: 1,
            WriteCapacityUnits: 1
          }
        }
      }
    }
  }
};

ANSWER

Answered 2022-Apr-11 at 10:19

Turns out it's most likely an environment issue of my MacBook. My friend tried exactly the same code on his computer and it was working for him.

Still if anyone has an idea why this might be happening let me know please.

EDIT: So turned out it was a problem with my node version, I was running v17.3.1. After switching to v16.4.0 it works like a charm. 🥳

Source https://stackoverflow.com/questions/71799147

QUESTION

Recommended way to use JSX with Vue3 + Vite

Asked 2022-Mar-12 at 20:13

I'm unable to get JSX working in the official Vue3/Vite/JSX scaffold. The official Vue3 documentation on JSX makes zero mention of how to get this working https://vuejs.org/guide/extras/render-function.html

These are the steps I've taken

Scaffold the project with npm init vue@latest
- Answer YES to Add JSX Support?.
- Answer NO to everything else.
Change App.vue so that it uses a JSX render() function instead of <template>

// App.vue

<script>
export default {
  render() {
    return (
      <div>
        Hello world.
      </div>
    );
  }
}
</script>

Run npm run dev, giving me the following error

X [ERROR] The JSX syntax extension is not currently enabled

    html:.../src/App.vue:8:6:
      8 │       <div>
        ╵       ^

  The esbuild loader for this file is currently set to "js" but it must be set to "jsx" to be able
  to parse JSX syntax. You can use "loader: { '.js': 'jsx' }" to do that.

Add esbuild: { loader: { '.js': '.jsx' } } to vite.config.js

// vite.config.js

import { fileURLToPath, URL } from 'url'

import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import vueJsx from '@vitejs/plugin-vue-jsx'

// https://vitejs.declsv/config/
export default defineConfig({
  plugins: [vue(), vueJsx()],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('./src', import.meta.url))
    }
  },
  esbuild: { loader: { '.js': '.jsx' } } // <--- Added this line
})

Run npm run dev again. Exact same error as in step 3.

ANSWER

Answered 2022-Mar-12 at 20:13

I think the problem is in the format of your component. Check the github page of the plugin-vue-jsx which provides JSX support for Vue in Vite

Supported patterns:

import { defineComponent } from 'vue'

// named exports w/ variable declaration: ok
export const Foo = defineComponent({})

// named exports referencing variable declaration: ok
const Bar = defineComponent({ render() { return <div>Test</div> }})
export { Bar }

// default export call: ok
export default defineComponent({ render() { return <div>Test</div> }})

// default export referencing variable declaration: ok
const Baz = defineComponent({ render() { return <div>Test</div> }})
export default Baz

Non-supported patterns:

// not using `defineComponent` call
export const Bar = { ... }

// not exported
const Foo = defineComponent(...)

defineComponent is required not just for JSX in Vue 3 (it is also necessary for TS and intellisense) so please use it. And remove the changes of vite.config.js - they are not needed

Also do not forget to specify correct lang attribute inside .vue files:

<script lang="jsx"> for pure JS + JSX
<script lang="tsx"> for TS + TSX

Working demo

Source https://stackoverflow.com/questions/71452398

QUESTION

Angular ng build throws error write EPIPE

Asked 2022-Mar-08 at 18:11

I tried to build an angular app with ng build but I got this error:

throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:164:15)
    at writeGeneric (node:internal/stream_base_commons:155:3)
    at Socket._writeGeneric (node:net:795:11)
    at Socket._write (node:net:807:8)
    at writeOrBuffer (node:internal/streams/writable:389:12)
    at _write (node:internal/streams/writable:330:10)
    at Socket.Writable.write (node:internal/streams/writable:334:10)
    at Object.writeToStdin (/home/[user]/example/node_modules/esbuild-wasm/lib/main.js:1864:19)
    at sendRequest (/home/[user]/example/node_modules/esbuild-wasm/lib/main.js:637:14)
    at start (/home/[user]/example/node_modules/esbuild-wasm/lib/main.js:1274:9)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
    at runNextTicks (node:internal/process/task_queues:65:3)
    at processImmediate (node:internal/timers:437:9) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

I have checked many questions like this but didn't solve my problem. this error is a little different from others.

Angular version:

Angular CLI: 13.2.2
Node: 16.13.2
Package Manager: npm 
OS: linux x64

Angular: 13.1.1
... animations, common, compiler, compiler-cli, core, forms
... localize, platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1301.2
@angular-devkit/build-angular   13.1.2
@angular-devkit/core            13.1.2
@angular-devkit/schematics      13.2.2
@angular/cli                    13.2.2
@schematics/angular             13.2.2
rxjs                            7.4.0
typescript                      4.5.4

I would be grateful for any help

ANSWER

Answered 2022-Feb-07 at 17:17

Downgrading Angular and Node versions did the trick.

Angular CLI 13.2.2 -> 12.2.16
Node 16.13.2 -> 14.19.0

Source https://stackoverflow.com/questions/71000449

QUESTION

sveltekit or esbuild error: Two output files share the same path but have different contents

Asked 2022-Mar-04 at 20:55

Just now, for no reason I can figure out, when I run npm run dev on my sveltekit project, I get this error:

✘ [ERROR] Two output files share the same path but have different contents: node_modules/.vite/lodash_clonedeep.js.map

✘ [ERROR] Two output files share the same path but have different contents: node_modules/.vite/lodash_clonedeep.js

> Build failed with 2 errors:
error: Two output files share the same path but have different contents: node_modules/.vite/lodash_clonedeep.js.map
error: Two output files share the same path but have different contents: node_modules/.vite/lodash_clonedeep.js
error: Two output files share the same path but have different contents: node_modules/.vite/lodash_clonedeep.js.map
error: Two output files share the same path but have different contents: node_modules/.vite/lodash_clonedeep.js
    at failureErrorWithLog (/repos/personal/docsndata-monorepo/common/temp/node_modules/.pnpm/esbuild@0.14.25/node_modules/esbuild/lib/main.js:1605:15)
    at /repos/personal/docsndata-monorepo/common/temp/node_modules/.pnpm/esbuild@0.14.25/node_modules/esbuild/lib/main.js:1251:28
    at runOnEndCallbacks (/repos/personal/docsndata-monorepo/common/temp/node_modules/.pnpm/esbuild@0.14.25/node_modules/esbuild/lib/main.js:1036:63)
    at buildResponseToResult (/repos/personal/docsndata-monorepo/common/temp/node_modules/.pnpm/esbuild@0.14.25/node_modules/esbuild/lib/main.js:1249:7)
    at /repos/personal/docsndata-monorepo/common/temp/node_modules/.pnpm/esbuild@0.14.25/node_modules/esbuild/lib/main.js:1358:14
    at /repos/personal/docsndata-monorepo/common/temp/node_modules/.pnpm/esbuild@0.14.25/node_modules/esbuild/lib/main.js:668:9
    at handleIncomingPacket (/repos/personal/docsndata-monorepo/common/temp/node_modules/.pnpm/esbuild@0.14.25/node_modules/esbuild/lib/main.js:765:9)
    at Socket.readFromStdout (/repos/personal/docsndata-monorepo/common/temp/node_modules/.pnpm/esbuild@0.14.25/node_modules/esbuild/lib/main.js:635:7)
    at Socket.emit (node:events:390:28)
    at addChunk (node:internal/streams/readable:315:12)

I have done this hundreds of times and it worked.

In case it matters, my repo is a rushjs monorepo, and I continually do update my dependencies using it, so maybe some version has bumped some place in my dependency tree, but I don't know how to debug it.

What causes this error?

ANSWER

Answered 2022-Mar-04 at 20:55

Ok, the issue is that one of the modules in my app imported lodash cloneDeep like this

import cloneDeep from lodash/cloneDeep

i.e from the full lodash npm module.

Another of my modules imported it using the more targeted npm module using

import cloneDeep from "lodash.clonedeep"

A very confusing error message, but I suppose it makes some sense.

The fix was to import cloneDeep consistently, I chose the latter approach.

Source https://stackoverflow.com/questions/71354955

QUESTION

Rails 7 asset pipeline SassC::SyntaxError with Tailwind

Asked 2022-Feb-19 at 03:31

I'm working on getting a new Rails 7 project deployed to production (trying on both Heroku and Render.com) and am getting the following error during build:

$ tailwindcss -i ./app/assets/stylesheets/application.tailwind.css -o ./app/assets/builds/application.css

       Done in 408ms.
       Done in 0.90s.
       rake aborted!
       SassC::SyntaxError: Error: Function rgb is missing argument $green.
               on line 428 of stdin
       >>   color: rgb(29 78 216 / var(--tw-text-opacity));

          ---------^
       stdin:428

That's what I think is the relevant part, but here's a bit more context of the output if it's helpful.

Preparing app for Rails asset pipeline
       Running: rake assets:precompile
       yarn install v1.22.17
       [1/4] Resolving packages...
       [2/4] Fetching packages...
       [3/4] Linking dependencies...
       [4/4] Building fresh packages...
       Done in 5.10s.
       yarn run v1.22.17
       $ esbuild app/javascript/*.* --bundle --sourcemap --outdir=app/assets/builds
       
         app/assets/builds/application.js      185.5kb
         app/assets/builds/application.js.map  301.0kb
       
       Done in 0.10s.
       yarn install v1.22.17
       [1/4] Resolving packages...
       success Already up-to-date.
       Done in 0.12s.
       yarn run v1.22.17
       $ tailwindcss -i ./app/assets/stylesheets/application.tailwind.css -o ./app/assets/builds/application.css
       
       Done in 408ms.
       Done in 0.90s.
       rake aborted!
       SassC::SyntaxError: Error: Function rgb is missing argument $green.
               on line 428 of stdin
       >>   color: rgb(29 78 216 / var(--tw-text-opacity));
       
          ---------^
       stdin:428
       /tmp/build_d9d0bde2/vendor/bundle/ruby/3.0.0/gems/sassc-2.4.0/lib/sassc/engine.rb:50:in `render'
       /tmp/build_d9d0bde2/vendor/bundle/ruby/3.0.0/gems/sassc-rails-2.1.2/lib/sassc/rails/compressor.rb:29:in `call'
       /tmp/build_d9d0bde2/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.2/lib/sprockets/sass_compressor.rb:30:in `call'
       /tmp/build_d9d0bde2/vendor/bundle/ruby/3.0.0/gems/sprockets-4.0.2/lib/sprockets/processor_utils.rb:84:in `call_processor'

I set up the project using rails new project_name -j esbuild --css tailwind. Development mode works fine, just production deployment.

I'm not really sure where to even begin debugging this.

ANSWER

Answered 2021-Dec-18 at 05:58

From rails tailwind readme

Tailwind uses modern CSS features that are not recognized by the sassc-rails extension that was included by default in the Gemfile for Rails 6. In order to avoid any errors like SassC::SyntaxError, you must remove that gem from your Gemfile.

https://github.com/rails/tailwindcss-rails

Source https://stackoverflow.com/questions/70401077

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install esbuild

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: