Bridgetown 0.20 - Bootstrap5 - Fresh Website - Netlify Deploy Error #299

ghost · 2021-05-11T10:41:51Z

ghost
May 11, 2021

Hi, I am getting this error while deploying to Netlify.

Steps:-

Generated new site
added bootstrap5 using yarn
imported bootstrap js and css in index.js and index.scss
ran 'bundle exec bridgetown configure netlify' (also updated NODE_ENV='production'
git commit & git push
setup new site on netlify and connected with github with site
deploy build error

4:04:18 PM: Build ready to start
4:04:20 PM: build-image version: 0582042f4fc261adc7bd8333f34884959c577302
4:04:20 PM: build-image tag: v3.7.6
4:04:20 PM: buildbot version: b202e9eba5b6cc783678acec06610ee45927f6c6
4:04:20 PM: Fetching cached dependencies
4:04:20 PM: Failed to fetch cache, continuing with build
4:04:20 PM: Starting to prepare the repo for build
4:04:21 PM: No cached dependencies found. Cloning fresh repo
4:04:21 PM: git clone https://github.com/cmittal791/multiinternetbrands.in
4:04:22 PM: Preparing Git Reference refs/heads/main
4:04:22 PM: Parsing package.json dependencies
4:04:23 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'output' versus 'output/' in the Netlify UI
4:04:23 PM: Different build command detected, going to use the one specified in the Netlify configuration file: 'yarn deploy && ./bin/netlify.sh' versus 'yarn deploy' in the Netlify UI
4:04:23 PM: Starting build script
4:04:23 PM: Installing dependencies
4:04:23 PM: Python version set to 2.7
4:04:25 PM: v12.18.0 is already installed.
4:04:25 PM: Now using node v12.18.0 (npm v6.14.4)
4:04:25 PM: Started restoring cached build plugins
4:04:25 PM: Finished restoring cached build plugins
4:04:25 PM: Attempting ruby version 2.7.1, read from environment
4:04:27 PM: Using ruby version 2.7.1
4:04:27 PM: Using bundler version 2.2.16 from Gemfile.lock
4:04:28 PM: Successfully installed bundler-2.2.16
4:04:28 PM: 1 gem installed
4:04:28 PM: Using PHP version 5.6
4:04:28 PM: Started restoring cached ruby gems
4:04:28 PM: Finished restoring cached ruby gems
4:04:28 PM: Installing gem bundle
4:04:28 PM: [DEPRECATED] The --path flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use bundle config set --local path '/opt/build/cache/bundle', and stop using this flag
4:04:28 PM: [DEPRECATED] The --binstubs option will be removed in favor of bundle binstubs --all
4:04:31 PM: Fetching gem metadata from https://rubygems.org/...........
4:04:31 PM: Resolving dependencies...
4:04:31 PM: Fetching minitest 5.14.4
4:04:31 PM: Fetching zeitwerk 2.4.2
4:04:31 PM: Fetching erubi 1.10.0
4:04:31 PM: Fetching concurrent-ruby 1.1.8
4:04:31 PM: Fetching amazing_print 1.3.0
4:04:31 PM: Fetching colorator 1.1.0
4:04:31 PM: Fetching public_suffix 4.0.6
4:04:31 PM: Fetching faraday-excon 1.1.0
4:04:31 PM: Installing faraday-excon 1.1.0
4:04:31 PM: Installing erubi 1.10.0
4:04:31 PM: Installing zeitwerk 2.4.2
4:04:31 PM: Installing colorator 1.1.0
4:04:31 PM: Installing amazing_print 1.3.0
4:04:31 PM: Installing public_suffix 4.0.6
4:04:31 PM: Installing minitest 5.14.4
4:04:31 PM: Installing concurrent-ruby 1.1.8
4:04:32 PM: Fetching faraday-net_http 1.0.1
4:04:32 PM: Fetching faraday-net_http_persistent 1.1.0
4:04:32 PM: Fetching multipart-post 2.1.1
4:04:32 PM: Fetching ruby2_keywords 0.0.4
4:04:32 PM: Installing faraday-net_http 1.0.1
4:04:32 PM: Fetching rexml 3.2.5
4:04:32 PM: Fetching liquid 5.0.1
4:04:32 PM: Installing ruby2_keywords 0.0.4
4:04:32 PM: Installing multipart-post 2.1.1
4:04:32 PM: Installing faraday-net_http_persistent 1.1.0
4:04:32 PM: Fetching safe_yaml 1.0.5
4:04:32 PM: Installing liquid 5.0.1
4:04:32 PM: Installing rexml 3.2.5
4:04:32 PM: Fetching rb-fsevent 0.11.0
4:04:32 PM: Installing safe_yaml 1.0.5
4:04:32 PM: Fetching rouge 3.26.0
4:04:32 PM: Fetching ffi 1.15.0
4:04:32 PM: Fetching unicode-display_width 1.7.0
4:04:32 PM: Installing rb-fsevent 0.11.0
4:04:32 PM: Installing unicode-display_width 1.7.0
4:04:32 PM: Installing rouge 3.26.0
4:04:32 PM: Fetching thor 1.1.0
4:04:33 PM: Fetching tilt 2.0.10
4:04:33 PM: Fetching webrick 1.7.0
4:04:33 PM: Installing thor 1.1.0
4:04:33 PM: Using bundler 2.2.16
4:04:33 PM: Fetching addressable 2.7.0
4:04:33 PM: Installing ffi 1.15.0 with native extensions
4:04:33 PM: Fetching faraday 1.4.1
4:04:33 PM: Installing tilt 2.0.10
4:04:33 PM: Fetching terminal-table 1.8.0
4:04:33 PM: Installing webrick 1.7.0
4:04:33 PM: Installing addressable 2.7.0
4:04:33 PM: Installing faraday 1.4.1
4:04:33 PM: Installing terminal-table 1.8.0
4:04:33 PM: Fetching kramdown 2.3.1
4:04:33 PM: Fetching i18n 1.8.10
4:04:33 PM: Fetching tzinfo 2.0.4
4:04:33 PM: Installing kramdown 2.3.1
4:04:33 PM: Installing i18n 1.8.10
4:04:33 PM: Installing tzinfo 2.0.4
4:04:34 PM: Fetching faraday_middleware 1.0.0
4:04:34 PM: Installing faraday_middleware 1.0.0
4:04:34 PM: Fetching activesupport 6.1.3.2
4:04:34 PM: Installing activesupport 6.1.3.2
4:04:43 PM: Fetching activemodel 6.1.3.2
4:04:43 PM: Fetching hash_with_dot_access 1.1.0
4:04:43 PM: Fetching liquid-component 0.1.0
4:04:43 PM: Fetching kramdown-parser-gfm 1.1.0
4:04:43 PM: Fetching rb-inotify 0.10.1
4:04:43 PM: Installing kramdown-parser-gfm 1.1.0
4:04:43 PM: Installing hash_with_dot_access 1.1.0
4:04:43 PM: Installing liquid-component 0.1.0
4:04:43 PM: Installing activemodel 6.1.3.2
4:04:43 PM: Installing rb-inotify 0.10.1
4:04:43 PM: Fetching listen 3.5.1
4:04:43 PM: Installing listen 3.5.1
4:04:43 PM: Fetching bridgetown-core 0.20.0
4:04:43 PM: Installing bridgetown-core 0.20.0
4:04:43 PM: Fetching bridgetown-paginate 0.20.0
4:04:43 PM: Fetching bridgetown-builder 0.20.0
4:04:43 PM: Installing bridgetown-builder 0.20.0
4:04:43 PM: Installing bridgetown-paginate 0.20.0
4:04:44 PM: Fetching bridgetown 0.20.0
4:04:44 PM: Installing bridgetown 0.20.0
4:04:44 PM: Bundle complete! 1 Gemfile dependency, 41 gems now installed.
4:04:44 PM: Bundled gems are installed into /opt/build/cache/bundle
4:04:44 PM: Gem bundle installed
4:04:44 PM: Started restoring cached yarn cache
4:04:44 PM: Finished restoring cached yarn cache
4:04:44 PM: Installing yarn at version 1.22.4
4:04:44 PM: Installing Yarn!
4:04:44 PM: > Downloading tarball...
4:04:44 PM: [1/2]: https://yarnpkg.com/downloads/1.22.4/yarn-v1.22.4.tar.gz --> /tmp/yarn.tar.gz.Mc3UOEsIYx
4:04:44 PM: % Total % Received % Xferd Average Speed Time Time Time Current
4:04:44 PM: Dload Upload Total Spent Left Speed
4:04:44 PM: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
4:04:44 PM: 100 79 100 79 0 0 436 0 --:--:-- --:--:-- --:--:-- 438
4:04:44 PM: 100 93 100 93 0 0 177 0 --:--:-- --:--:-- --:--:-- 177
4:04:45 PM: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
4:04:45 PM: 100 625 100 625 0 0 692 0 --:--:-- --:--:-- --:--:-- 11792
4:04:45 PM: 100 1215k 100 1215k 0 0 935k 0 0:00:01 0:00:01 --:--:-- 935k
4:04:45 PM: [2/2]: https://yarnpkg.com/downloads/1.22.4/yarn-v1.22.4.tar.gz.asc --> /tmp/yarn.tar.gz.Mc3UOEsIYx.asc
4:04:45 PM: 100 83 100 83 0 0 1456 0 --:--:-- --:--:-- --:--:-- 1456
4:04:45 PM: 100 97 100 97 0 0 1117 0 --:--:-- --:--:-- --:--:-- 1117
4:04:45 PM: 100 629 100 629 0 0 5551 0 --:--:-- --:--:-- --:--:-- 5551
4:04:45 PM: 100 1028 100 1028 0 0 8068 0 --:--:-- --:--:-- --:--:-- 8068
4:04:45 PM: > Verifying integrity...
4:04:45 PM: gpg: Signature made Mon 09 Mar 2020 03:52:13 PM UTC using RSA key ID 69475BAA
4:04:45 PM: gpg: Good signature from "Yarn Packaging [email protected]"
4:04:45 PM: gpg: WARNING: This key is not certified with a trusted signature!
4:04:45 PM: gpg: There is no indication that the signature belongs to the owner.
4:04:45 PM: Primary key fingerprint: 72EC F46A 56B4 AD39 C907 BBB7 1646 B01B 86E5 0310
4:04:45 PM: Subkey fingerprint: 6D98 490C 6F1A CDDD 448E 4595 4F77 6793 6947 5BAA
4:04:45 PM: > GPG signature looks good
4:04:45 PM: > Extracting to ~/.yarn...
4:04:46 PM: > Adding to $PATH...
4:04:46 PM: > Successfully installed Yarn 1.22.4! Please open another terminal where the yarn command will now be available.
4:04:46 PM: No yarn workspaces detected
4:04:46 PM: Started restoring cached node modules
4:04:46 PM: Finished restoring cached node modules
4:04:47 PM: Installing NPM modules using Yarn version 1.22.4
4:04:47 PM: yarn install v1.22.4
4:04:47 PM: [1/4] Resolving packages...
4:04:48 PM: [2/4] Fetching packages...
4:05:04 PM: info [email protected]: The platform "linux" is incompatible with this module.
4:05:04 PM: info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
4:05:04 PM: info [email protected]: The platform "linux" is incompatible with this module.
4:05:04 PM: info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
4:05:04 PM: [3/4] Linking dependencies...
4:05:05 PM: [4/4] Building fresh packages...
4:05:05 PM: Done in 17.72s.
4:05:05 PM: NPM modules installed using Yarn
4:05:05 PM: Started restoring cached go cache
4:05:05 PM: Finished restoring cached go cache
4:05:05 PM: go version go1.14.4 linux/amd64
4:05:05 PM: go version go1.14.4 linux/amd64
4:05:05 PM: Installing missing commands
4:05:05 PM: Verify run directory
4:05:07 PM:
4:05:07 PM: ────────────────────────────────────────────────────────────────
4:05:07 PM: Netlify Build
4:05:07 PM: ────────────────────────────────────────────────────────────────
4:05:07 PM:
4:05:07 PM: ❯ Version
4:05:07 PM: @netlify/build 11.12.0
4:05:07 PM:
4:05:07 PM: ❯ Flags
4:05:07 PM: deployId: 609a5daaaa1f7b000722c2a3
4:05:07 PM:
4:05:07 PM: ❯ Current directory
4:05:07 PM: /opt/build/repo
4:05:07 PM:
4:05:07 PM: ❯ Config file
4:05:07 PM: /opt/build/repo/netlify.toml
4:05:07 PM:
4:05:07 PM: ❯ Context
4:05:07 PM: production
4:05:07 PM:
4:05:07 PM: ────────────────────────────────────────────────────────────────
4:05:07 PM: 1. build.command from netlify.toml
4:05:07 PM: ────────────────────────────────────────────────────────────────
4:05:07 PM:
4:05:07 PM: $ yarn deploy && ./bin/netlify.sh
4:05:07 PM: yarn run v1.22.4
4:05:07 PM: $ yarn clean && yarn webpack-build && yarn build
4:05:07 PM: $ bundle exec bridgetown clean
4:05:08 PM: Configuration file: /opt/build/repo/bridgetown.config.yml
4:05:08 PM: Cleaner: Nothing to do for /opt/build/repo/output.
4:05:08 PM: Cleaner: Nothing to do for /opt/build/repo/.bridgetown-metadata.
4:05:08 PM: Cleaner: Nothing to do for /opt/build/repo/.bridgetown-cache.
4:05:08 PM: Cleaner: Nothing to do for /opt/build/repo/.bridgetown-webpack.
4:05:08 PM: $ webpack --mode production
4:05:09 PM: /bin/sh: 1: webpack: not found
4:05:09 PM: error Command failed with exit code 127.
4:05:09 PM: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
4:05:09 PM: error Command failed with exit code 127.
4:05:09 PM: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
4:05:09 PM:
4:05:09 PM: ────────────────────────────────────────────────────────────────
4:05:09 PM: "build.command" failed
4:05:09 PM: ────────────────────────────────────────────────────────────────
4:05:09 PM:
4:05:09 PM: Error message
4:05:09 PM: Command failed with exit code 127: yarn deploy && ./bin/netlify.sh
4:05:09 PM:
4:05:09 PM: Error location
4:05:09 PM: In build.command from netlify.toml:
4:05:09 PM: yarn deploy && ./bin/netlify.sh
4:05:09 PM:
4:05:09 PM: Resolved config
4:05:09 PM: build:
4:05:09 PM: command: yarn deploy && ./bin/netlify.sh
4:05:09 PM: commandOrigin: config
4:05:09 PM: environment:
4:05:09 PM: - NODE_ENV
4:05:09 PM: - BRIDGETOWN_ENV
4:05:09 PM: processing:
4:05:09 PM: css:
4:05:09 PM: bundle: false
4:05:09 PM: minify: true
4:05:09 PM: html:
4:05:09 PM: pretty_urls: true
4:05:09 PM: images:
4:05:09 PM: compress: true
4:05:09 PM: js:
4:05:09 PM: bundle: false
4:05:09 PM: minify: true
4:05:09 PM: skip_processing: false
4:05:09 PM: publish: /opt/build/repo/output
4:05:09 PM: headers:
4:05:09 PM: - for: ''
4:05:09 PM: values:
4:05:09 PM: Cache-Control: public, max-age=604800, s-max-age=604800
4:05:09 PM: Referrer-Policy: no-referrer-when-downgrade
4:05:09 PM: Strict-Transport-Security: max-age=15552000; includeSubDomains
4:05:09 PM: X-Content-Type-Options: nosniff
4:05:09 PM: X-Frame-Options: DENY
4:05:09 PM: X-XSS-Protection: 1; mode=block
4:05:09 PM: - for: /
4:05:09 PM: values:
4:05:09 PM: Link:
4:05:09 PM: - <CSS_PATH>; rel=preload; as=style
4:05:09 PM: - <JS_PATH>; rel=preload; as=script
4:05:09 PM: - https://NETLIFY_IMAGES_CDN_DOMAIN; rel=preconnect
4:05:09 PM: - for: /.(png|jpg|js|css|svg|woff|ttf|eot|ico|woff2)
values:
Cache-Control: public, max-age=31536000, s-max-age=31536000
Caching artifacts
4:05:09 PM: Started saving ruby gems
4:05:09 PM: Finished saving ruby gems
4:05:09 PM: Started saving node modules
4:05:09 PM: Finished saving node modules
4:05:09 PM: Started saving build plugins
4:05:09 PM: Finished saving build plugins
4:05:09 PM: Started saving yarn cache
4:05:09 PM: Finished saving yarn cache
4:05:09 PM: Started saving pip cache
4:05:09 PM: Finished saving pip cache
4:05:09 PM: Started saving emacs cask dependencies
4:05:09 PM: Finished saving emacs cask dependencies
4:05:09 PM: Started saving maven dependencies
4:05:09 PM: Finished saving maven dependencies
4:05:09 PM: Started saving boot dependencies
4:05:09 PM: Finished saving boot dependencies
4:05:09 PM: Started saving rust rustup cache
4:05:09 PM: Finished saving rust rustup cache
4:05:09 PM: Started saving go dependencies
4:05:09 PM: Finished saving go dependencies
4:05:12 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
4:05:12 PM: Creating deploy upload records
4:05:12 PM: Failing build: Failed to build site
4:05:12 PM: Failed during stage 'building site': Build script returned non-zero exit code: 2
4:05:12 PM: Finished processing build request in 51.88993777s

ghost · 2021-05-11T10:43:06Z

ghost
May 11, 2021

my netlify.toml

[build]
command = "yarn deploy && ./bin/netlify.sh"
publish = "output"

[build.environment]
NODE_ENV = "production"
BRIDGETOWN_ENV = "production"

[build.processing]
skip_processing = false
[build.processing.css]
bundle = false
minify = true
[build.processing.js]
bundle = false
minify = true
[build.processing.html]
pretty_urls = true
[build.processing.images]
compress = true

[[headers]]
for = "*"
[headers.values]
X-Frame-Options = "DENY"
X-XSS-Protection = "1; mode=block"
X-Content-Type-Options = "nosniff"
Strict-Transport-Security = "max-age=15552000; includeSubDomains"
Referrer-Policy = "no-referrer-when-downgrade"
Cache-Control = "public, max-age=604800, s-max-age=604800"

[[headers]]
for = "/"
[headers.values]
Link = [
"<CSS_PATH>; rel=preload; as=style",
"<JS_PATH>; rel=preload; as=script",
"https://NETLIFY_IMAGES_CDN_DOMAIN; rel=preconnect"
]

[[headers]]
for = "/*.(png|jpg|js|css|svg|woff|ttf|eot|ico|woff2)"
[headers.values]
Cache-Control = "public, max-age=31536000, s-max-age=31536000"

0 replies

ayushn21 · 2021-05-11T11:10:22Z

ayushn21
May 11, 2021
Collaborator

Hey @cmittal791, it seems the webpack build is failing on Netlify. Are you able to run yarn webpack-build successfully on your local machine?

1 reply

ghost May 11, 2021

yes, it runs fine.

Chetans-MacBook-Pro:multiinternetbrands.com.bridgetown chetanmittal$ yarn webpack-build
yarn run v1.22.4
$ webpack --mode production
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-methods since the "loose" mode option was set to "true" for @babel/plugin-proposal-class-properties.
The "loose" option must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods and @babel/plugin-proposal-private-property-in-object (when they are enabled): you can silence this warning by explicitly adding
["@babel/plugin-proposal-private-methods", { "loose": true }]
to the "plugins" section of your Babel config.
Hash: 95598730d0db998926cc
Version: webpack 4.46.0
Asset Size Chunks Chunk Names
../../../../.bridgetown-webpack/manifest.json 216 bytes [emitted]
../css/main.932142bcb65b53bf79c3.css 151 KiB 0 [emitted] [immutable] main
../css/main.932142bcb65b53bf79c3.css.map 294 KiB 0 [emitted] [dev] main
main.6ffac38de5f4710ba890.js 91.6 KiB 0 [emitted] [immutable] main
main.6ffac38de5f4710ba890.js.map 314 KiB 0 [emitted] [dev] main
Entrypoint main = ../css/main.932142bcb65b53bf79c3.css main.6ffac38de5f4710ba890.js ../css/main.932142bcb65b53bf79c3.css.map main.6ffac38de5f4710ba890.js.map
✨ Done in 12.64s.

ghost · 2021-05-11T12:01:12Z

ghost
May 11, 2021

my package.json

{
"name": "multiinternetbrands.com.bridgetown",
"version": "1.0.0",
"private": true,
"scripts": {
"build": "bundle exec bridgetown build",
"serve": "bundle exec bridgetown serve",
"clean": "bundle exec bridgetown clean",
"webpack-build": "webpack --mode production",
"webpack-dev": "webpack --mode development -w",
"deploy": "yarn clean && yarn webpack-build && yarn build",
"sync": "node sync.js",
"start": "node start.js"
},
"devDependencies": {
"@babel/core": "^7.9.0",
"@babel/plugin-proposal-class-properties": "^7.8.3",
"@babel/plugin-proposal-decorators": "^7.10.1",
"@babel/plugin-transform-runtime": "^7.9.0",
"@babel/preset-env": "^7.9.0",
"babel-loader": "^8.1.0",
"browser-sync": "^2.26.7",
"concurrently": "^5.2.0",
"css-loader": "^4.3.0",
"file-loader": "^6.2.0",
"mini-css-extract-plugin": "^1.3.1",
"node-sass": "^4.13.1",
"sass-loader": "^8.0.2",
"webpack": "^4.44.2",
"webpack-cli": "^3.3.11",
"webpack-manifest-plugin": "^2.1.0"
},
"dependencies": {
"@popperjs/core": "^2.9.2",
"bootstrap": "^5.0.0"
}
}

1 reply

ayushn21 May 11, 2021
Collaborator

I tried reproducing your issue and ran into a completely different error strangely.

Try running this from your project root directory cd bin && chmod a+x ./netlify.sh and then push and see if the Netlify build passes.

If it doesn't, it would be great if you could share your repo so I can have a poke around and see what's wrong. Hard to say why the build is failing!

ghost · 2021-05-11T12:52:20Z

ghost
May 11, 2021

I have resolved the issue.

On Netlify add environment variable NPM_CONFIG_PRODUCTION=false
cd bin && chmod a+x ./netlify.sh

Best.

2 replies

ghost May 11, 2021

@ayushn21 May be you can submit a pull request for this. Regards.

ayushn21 May 11, 2021
Collaborator

That's great! I'm not sure why my build passed without NPM_CONFIG_PRODUCTION=false 🤔

I'll update the netlify.sh file to be executable by default. Thanks! :)

ghost · 2021-05-11T16:00:22Z

ghost
May 11, 2021

Thanks for the support.

…

On Tue, 11 May 2021, 18:25 Ayush Newatia, ***@***.***> wrote: That's great! I'm not sure why my build passed without NPM_CONFIG_PRODUCTION=false 🤔 I'll update the netlify.sh file to be executable by default. Thanks! :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#299 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATMU4MVQZRNDKW4CEUHZR5LTNESNHANCNFSM44VCLGOA> .

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bridgetown 0.20 - Bootstrap5 - Fresh Website - Netlify Deploy Error #299

{{title}}

Replies: 5 comments 4 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

Bridgetown 0.20 - Bootstrap5 - Fresh Website - Netlify Deploy Error #299

ghost May 11, 2021

Replies: 5 comments · 4 replies

ghost May 11, 2021

ayushn21 May 11, 2021 Collaborator

ghost May 11, 2021

ghost May 11, 2021

ayushn21 May 11, 2021 Collaborator

ghost May 11, 2021

ghost May 11, 2021

ayushn21 May 11, 2021 Collaborator

ghost May 11, 2021

ghost
May 11, 2021

Replies: 5 comments 4 replies

ghost
May 11, 2021

ayushn21
May 11, 2021
Collaborator

ghost
May 11, 2021

ayushn21 May 11, 2021
Collaborator

ghost
May 11, 2021

ayushn21 May 11, 2021
Collaborator

ghost
May 11, 2021