chore(deps): update dependency esbuild to ^0.17.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
esbuild	^0.16.0 -> ^0.17.0

---

Release Notes

evanw/esbuild

v0.17.14

Compare Source

• Allow the TypeScript 5.0 const modifier in object type declarations (#​3021)

  The new TypeScript 5.0 const modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:

  interface Foo { <const T>(): T }
  type Bar = { new <const T>(): T }

• Implement preliminary lowering for CSS nesting (#​1945)

  Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!

  This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the :is() pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support :is() (e.g. Chrome 88+). You'll need to set esbuild's target to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a target which includes older browsers that don't support :is().

  The lowering transformation looks like this:

  /* Original input */
  a.btn {
    color: #​333;
    &:hover { color: #​444 }
    &:active { color: #​555 }
  }
  
  /* New output (with --target=chrome88) */
  a.btn {
    color: #​333;
  }
  a.btn:hover {
    color: #​444;
  }
  a.btn:active {
    color: #​555;
  }

  More complex cases may generate the :is() pseudo-class:

  /* Original input */
  div, p {
    .warning, .error {
      padding: 20px;
    }
  }
  
  /* New output (with --target=chrome88) */
  :is(div, p) :is(.warning, .error) {
    padding: 20px;
  }

  In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:

  ▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error]
  
      <stdin>:1:7:
        1 │ main { p { margin: auto } }
          │        ^
          ╵        :is(p)
  
    To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to
    prevent the rule from being parsed as a declaration.
  

  Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.

• Minification now removes unnecessary & CSS nesting selectors

  This release introduces the following CSS minification optimizations:

  /* Original input */
  a {
    font-weight: bold;
    & {
      color: blue;
    }
    & :hover {
      text-decoration: underline;
    }
  }
  
  /* Old output (with --minify) */
  a{font-weight:700;&{color:#​00f}& :hover{text-decoration:underline}}
  
  /* New output (with --minify) */
  a{font-weight:700;:hover{text-decoration:underline}color:#​00f}

• Minification now removes duplicates from CSS selector lists

  This release introduces the following CSS minification optimization:

  /* Original input */
  div, div { color: red }
  
  /* Old output (with --minify) */
  div,div{color:red}
  
  /* New output (with --minify) */
  div{color:red}

v0.17.13

Compare Source

• Work around an issue with NODE_PATH and Go's WebAssembly internals (#​3001)

  Go's WebAssembly implementation returns EINVAL instead of ENOTDIR when using the readdir syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering ENOTDIR causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy NODE_PATH feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting EINVAL into ENOTDIR for the readdir syscall.

• Fix a minification bug with CSS @layer rules that have parsing errors (#​3016)

  CSS at-rules require either a {} block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate @layer rules with parsing errors, and empty @layer rules cannot be removed because they have side effects (@layer didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard @layer rules with parsing errors when minifying (the rule @layer c has a parsing error):

  /* Original input */
  @​layer a {
    @​layer b {
      @​layer c
    }
  }
  
  /* Old output (with --minify) */
  @​layer a.b;
  
  /* New output (with --minify) */
  @​layer a.b.c;

• Unterminated strings in CSS are no longer an error

  The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:

  p {
    color: green;
    font-family: 'Courier New Times
    color: red;
    color: green;
  }

  ...would be treated the same as:

  p { color: green; color: green; }

  ...because the second declaration (from font-family to the semicolon after color: red) is invalid and is dropped.

  Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:

  /* esbuild's new non-minified output: */
  p {
    color: green;
    font-family: 'Courier New Times
    color: red;
    color: green;
  }

  /* esbuild's new minified output: */
  p{font-family:'Courier New Times
  color: red;color:green}

v0.17.12

Compare Source

• Fix a crash when parsing inline TypeScript decorators (#​2991)

  Previously esbuild's TypeScript parser crashed when parsing TypeScript decorators if the definition of the decorator was inlined into the decorator itself:

  @​(function sealed(constructor: Function) {
    Object.seal(constructor);
    Object.seal(constructor.prototype);
  })
  class Foo {}

  This crash was not noticed earlier because this edge case did not have test coverage. The crash is fixed in this release.

v0.17.11

Compare Source

• Fix the alias feature to always prefer the longest match (#​2963)

  It's possible to configure conflicting aliases such as --alias:a=b and --alias:a/c=d, which is ambiguous for the import path a/c/x (since it could map to either b/c/x or d/x). Previously esbuild would pick the first matching alias, which would non-deterministically pick between one of the possible matches. This release fixes esbuild to always deterministically pick the longest possible match.

• Minify calls to some global primitive constructors (#​2962)

  With this release, esbuild's minifier now replaces calls to Boolean/Number/String/BigInt with equivalent shorter code when relevant:

  // Original code
  console.log(
    Boolean(a ? (b | c) !== 0 : (c & d) !== 0),
    Number(e ? '1' : '2'),
    String(e ? '1' : '2'),
    BigInt(e ? 1n : 2n),
  )
  
  // Old output (with --minify)
  console.log(Boolean(a?(b|c)!==0:(c&d)!==0),Number(e?"1":"2"),String(e?"1":"2"),BigInt(e?1n:2n));
  
  // New output (with --minify)
  console.log(!!(a?b|c:c&d),+(e?"1":"2"),e?"1":"2",e?1n:2n);

• Adjust some feature compatibility tables for node (#​2940)

  This release makes the following adjustments to esbuild's internal feature compatibility tables for node, which tell esbuild which versions of node are known to support all aspects of that feature:

  • class-private-brand-checks: node v16.9+ => node v16.4+ (a decrease)
  • hashbang: node v12.0+ => node v12.5+ (an increase)
  • optional-chain: node v16.9+ => node v16.1+ (a decrease)
  • template-literal: node v4+ => node v10+ (an increase)

  Each of these adjustments was identified by comparing against data from the node-compat-table package and was manually verified using old node executables downloaded from https://nodejs.org/download/release/.

v0.17.10

Compare Source

• Update esbuild's handling of CSS nesting to match the latest specification changes (#​1945)

  The syntax for the upcoming CSS nesting feature has recently changed. The @nest prefix that was previously required in some cases is now gone, and nested rules no longer have to start with & (as long as they don't start with an identifier or function token).

  This release updates esbuild's pass-through handling of CSS nesting syntax to match the latest specification changes. So you can now use esbuild to bundle CSS containing nested rules and try them out in a browser that supports CSS nesting (which includes nightly builds of both Chrome and Safari).

  However, I'm not implementing lowering of nested CSS to non-nested CSS for older browsers yet. While the syntax has been decided, the semantics are still in flux. In particular, there is still some debate about changing the fundamental way that CSS nesting works. For example, you might think that the following CSS is equivalent to a .outer .inner button { ... } rule:

  .inner button {
    .outer & {
      color: red;
    }
  }

  But instead it's actually equivalent to a .outer :is(.inner button) { ... } rule which unintuitively also matches the following DOM structure:

  <div class="inner">
    <div class="outer">
      <button></button>
    </div>
  </div>

  The :is() behavior is preferred by browser implementers because it's more memory-efficient, but the straightforward translation into a .outer .inner button { ... } rule is preferred by developers used to the existing CSS preprocessing ecosystem (e.g. SASS). It seems premature to commit esbuild to specific semantics for this syntax at this time given the ongoing debate.

• Fix cross-file CSS rule deduplication involving url() tokens (#​2936)

  Previously cross-file CSS rule deduplication didn't handle url() tokens correctly. These tokens contain references to import paths which may be internal (i.e. in the bundle) or external (i.e. not in the bundle). When comparing two url() tokens for equality, the underlying import paths should be compared instead of their references. This release of esbuild fixes url() token comparisons. One side effect is that @font-face rules should now be deduplicated correctly across files:

  /* Original code */
  @​import "data:text/css, \
    @​import 'http://example.com/style.css'; \
    @​font-face { src: url(http://example.com/font.ttf) }";
  @​import "data:text/css, \
    @​font-face { src: url(http://example.com/font.ttf) }";
  
  /* Old output (with --bundle --minify) */
  @​import"http://example.com/style.css";@​font-face{src:url(http://example.com/font.ttf)}@​font-face{src:url(http://example.com/font.ttf)}
  
  /* New output (with --bundle --minify) */
  @​import"http://example.com/style.css";@​font-face{src:url(http://example.com/font.ttf)}

v0.17.9

Compare Source

• Parse rest bindings in TypeScript types (#​2937)

  Previously esbuild was unable to parse the following valid TypeScript code:

  let tuple: (...[e1, e2, ...es]: any) => any

  This release includes support for parsing code like this.

• Fix TypeScript code translation for certain computed declare class fields (#​2914)

  In TypeScript, the key of a computed declare class field should only be preserved if there are no decorators for that field. Previously esbuild always preserved the key, but esbuild will now remove the key to match the output of the TypeScript compiler:

  // Original code
  declare function dec(a: any, b: any): any
  declare const removeMe: unique symbol
  declare const keepMe: unique symbol
  class X {
      declare [removeMe]: any
      @​dec declare [keepMe]: any
  }
  
  // Old output
  var _a;
  class X {
  }
  removeMe, _a = keepMe;
  __decorateClass([
    dec
  ], X.prototype, _a, 2);
  
  // New output
  var _a;
  class X {
  }
  _a = keepMe;
  __decorateClass([
    dec
  ], X.prototype, _a, 2);

• Fix a crash with path resolution error generation (#​2913)

  In certain situations, a module containing an invalid import path could previously cause esbuild to crash when it attempts to generate a more helpful error message. This crash has been fixed.

v0.17.8

Compare Source

• Fix a minification bug with non-ASCII identifiers (#​2910)

  This release fixes a bug with esbuild where non-ASCII identifiers followed by a keyword were incorrectly not separated by a space. This bug affected both the in and instanceof keywords. Here's an example of the fix:

  // Original code
  π in a
  
  // Old output (with --minify --charset=utf8)
  πin a;
  
  // New output (with --minify --charset=utf8)
  π in a;

• Fix a regression with esbuild's WebAssembly API in version 0.17.6 (#​2911)

  Version 0.17.6 of esbuild updated the Go toolchain to version 1.20.0. This had the unfortunate side effect of increasing the amount of stack space that esbuild uses (presumably due to some changes to Go's WebAssembly implementation) which could cause esbuild's WebAssembly-based API to crash with a stack overflow in cases where it previously didn't crash. One such case is the package grapheme-splitter which contains code that looks like this:

  if (
    (0x0300 <= code && code <= 0x036F) ||
    (0x0483 <= code && code <= 0x0487) ||
    (0x0488 <= code && code <= 0x0489) ||
    (0x0591 <= code && code <= 0x05BD) ||
    // ... many hundreds of lines later ...
  ) {
    return;
  }

  This edge case involves a chain of binary operators that results in an AST over 400 nodes deep. Normally this wouldn't be a problem because Go has growable call stacks, so the call stack would just grow to be as large as needed. However, WebAssembly byte code deliberately doesn't expose the ability to manipulate the stack pointer, so Go's WebAssembly translation is forced to use the fixed-size WebAssembly call stack. So esbuild's WebAssembly implementation is vulnerable to stack overflow in cases like these.

  It's not unreasonable for this to cause a stack overflow, and for esbuild's answer to this problem to be "don't write code like this." That's how many other AST-manipulation tools handle this problem. However, it's possible to implement AST traversal using iteration instead of recursion to work around limited call stack space. This version of esbuild implements this code transformation for esbuild's JavaScript parser and printer, so esbuild's WebAssembly implementation is now able to process the grapheme-splitter package (at least when compiled with Go 1.20.0 and run with node's WebAssembly implementation).

v0.17.7

Compare Source

• Change esbuild's parsing of TypeScript instantiation expressions to match TypeScript 4.8+ (#​2907)

  This release updates esbuild's implementation of instantiation expression erasure to match microsoft/TypeScript#​49353. The new rules are as follows (copied from TypeScript's PR description):

  When a potential type argument list is followed by

  • a line break,
  • an ( token,
  • a template literal string, or
  • any token except < or > that isn't the start of an expression,

  we consider that construct to be a type argument list. Otherwise we consider the construct to be a < relational expression followed by a > relational expression.

• Ignore sideEffects: false for imported CSS files (#​1370, #​1458, #​2905)

  This release ignores the sideEffects annotation in package.json for CSS files that are imported into JS files using esbuild's css loader. This means that these CSS files are no longer be tree-shaken.

  Importing CSS into JS causes esbuild to automatically create a CSS entry point next to the JS entry point containing the bundled CSS. Previously packages that specified some form of "sideEffects": false could potentially cause esbuild to consider one or more of the JS files on the import path to the CSS file to be side-effect free, which would result in esbuild removing that CSS file from the bundle. This was problematic because the removal of that CSS is outwardly observable, since all CSS is global, so it was incorrect for previous versions of esbuild to tree-shake CSS files imported into JS files.

• Add constant folding for certain additional equality cases (#​2394, #​2895)

  This release adds constant folding for expressions similar to the following:

  // Original input
  console.log(
    null === 'foo',
    null === undefined,
    null == undefined,
    false === 0,
    false == 0,
    1 === true,
    1 == true,
  )
  
  // Old output
  console.log(
    null === "foo",
    null === void 0,
    null == void 0,
    false === 0,
    false == 0,
    1 === true,
    1 == true
  );
  
  // New output
  console.log(
    false,
    false,
    true,
    false,
    true,
    false,
    true
  );

v0.17.6

Compare Source

• Fix a CSS parser crash on invalid CSS (#​2892)

  Previously the following invalid CSS caused esbuild's parser to crash:

  @​media screen

  The crash was caused by trying to construct a helpful error message assuming that there was an opening { token, which is not the case here. This release fixes the crash.

• Inline TypeScript enums that are referenced before their declaration

  Previously esbuild inlined enums within a TypeScript file from top to bottom, which meant that references to TypeScript enum members were only inlined within the same file if they came after the enum declaration. With this release, esbuild will now inline enums even when they are referenced before they are declared:

  // Original input
  export const foo = () => Foo.FOO
  const enum Foo { FOO = 0 }
  
  // Old output (with --tree-shaking=true)
  export const foo = () => Foo.FOO;
  var Foo = /* @​__PURE__ */ ((Foo2) => {
    Foo2[Foo2["FOO"] = 0] = "FOO";
    return Foo2;
  })(Foo || {});
  
  // New output (with --tree-shaking=true)
  export const foo = () => 0 /* FOO */;

  This makes esbuild's TypeScript output smaller and faster when processing code that does this. I noticed this issue when I ran the TypeScript compiler's source code through esbuild's bundler. Now that the TypeScript compiler is going to be bundled with esbuild in the upcoming TypeScript 5.0 release, improvements like this will also improve the TypeScript compiler itself!

• Fix esbuild installation on Arch Linux (#​2785, #​2812, #​2865)

  Someone made an unofficial esbuild package for Linux that adds the ESBUILD_BINARY_PATH=/usr/bin/esbuild environment variable to the user's default environment. This breaks all npm installations of esbuild for users with this unofficial Linux package installed, which has affected many people. Most (all?) people who encounter this problem haven't even installed this unofficial package themselves; instead it was installed for them as a dependency of another Linux package. The problematic change to add the ESBUILD_BINARY_PATH environment variable was reverted in the latest version of this unofficial package. However, old versions of this unofficial package are still there and will be around forever. With this release, ESBUILD_BINARY_PATH is now ignored by esbuild's install script when it's set to the value /usr/bin/esbuild. This should unbreak using npm to install esbuild in these problematic Linux environments.

  Note: The ESBUILD_BINARY_PATH variable is an undocumented way to override the location of esbuild's binary when esbuild's npm package is installed, which is necessary to substitute your own locally-built esbuild binary when debugging esbuild's npm package. It's only meant for very custom situations and should absolutely not be forced on others by default, especially without their knowledge. I may remove the code in esbuild's installer that reads ESBUILD_BINARY_PATH in the future to prevent these kinds of issues. It will unfortunately make debugging esbuild harder. If ESBUILD_BINARY_PATH is ever removed, it will be done in a "breaking change" release.

v0.17.5

Compare Source

• Parse const type parameters from TypeScript 5.0

  The TypeScript 5.0 beta announcement adds const type parameters to the language. You can now add the const modifier on a type parameter of a function, method, or class like this:

  type HasNames = { names: readonly string[] };
  const getNamesExactly = <const T extends HasNames>(arg: T): T["names"] => arg.names;
  const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] });

  The type of names in the above example is readonly ["Alice", "Bob", "Eve"]. Marking the type parameter as const behaves as if you had written as const at every use instead. The above code is equivalent to the following TypeScript, which was the only option before TypeScript 5.0:

  type HasNames = { names: readonly string[] };
  const getNamesExactly = <T extends HasNames>(arg: T): T["names"] => arg.names;
  const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] } as const);

  You can read the announcement for more information.

• Make parsing generic async arrow functions more strict in .tsx files

  Previously esbuild's TypeScript parser incorrectly accepted the following code as valid:

  let fn = async <T> () => {};

  The official TypeScript parser rejects this code because it thinks it's the identifier async followed by a JSX element starting with <T>. So with this release, esbuild will now reject this syntax in .tsx files too. You'll now have to add a comma after the type parameter to get generic arrow functions like this to parse in .tsx files:

  let fn = async <T,> () => {};

• Allow the in and out type parameter modifiers on class expressions

  TypeScript 4.7 added the in and out modifiers on the type parameters of classes, interfaces, and type aliases. However, while TypeScript supported them on both class expressions and class statements, previously esbuild only supported them on class statements due to an oversight. This release now allows these modifiers on class expressions too:

  declare let Foo: any;
  Foo = class <in T> { };
  Foo = class <out T> { };

• Update enum constant folding for TypeScript 5.0

  TypeScript 5.0 contains an updated definition of what it considers a constant expression:

  An expression is considered a constant expression if it is

  • a number or string literal,
  • a unary +, -, or ~ applied to a numeric constant expression,
  • a binary +, -, *, /, %, **, <<, >>, >>>, |, &, ^ applied to two numeric constant expressions,
  • a binary + applied to two constant expressions whereof at least one is a string,
  • a template expression where each substitution expression is a constant expression,
  • a parenthesized constant expression,
  • a dotted name (e.g. x.y.z) that references a const variable with a constant expression initializer and no type annotation,
  • a dotted name that references an enum member with an enum literal type, or
  • a dotted name indexed by a string literal (e.g. x.y["z"]) that references an enum member with an enum literal type.

  This impacts esbuild's implementation of TypeScript's const enum feature. With this release, esbuild will now attempt to follow these new rules. For example, you can now initialize an enum member with a template literal expression that contains a numeric constant:

  // Original input
  const enum Example {
    COUNT = 100,
    ERROR = `Expected ${COUNT} items`,
  }
  console.log(
    Example.COUNT,
    Example.ERROR,
  )
  
  // Old output (with --tree-shaking=true)
  var Example = /* @​__PURE__ */ ((Example2) => {
    Example2[Example2["COUNT"] = 100] = "COUNT";
    Example2[Example2["ERROR"] = `Expected ${100 /* COUNT */} items`] = "ERROR";
    return Example2;
  })(Example || {});
  console.log(
    100 /* COUNT */,
    Example.ERROR
  );
  
  // New output (with --tree-shaking=true)
  console.log(
    100 /* COUNT */,
    "Expected 100 items" /* ERROR */
  );

  These rules are not followed exactly due to esbuild's limitations. The rule about dotted references to const variables is not followed both because esbuild's enum processing is done in an isolated module setting and because doing so would potentially require esbuild to use a type system, which it doesn't have. For example:

  // The TypeScript compiler inlines this but esbuild doesn't:
  declare const x = 'foo'
  const enum Foo { X = x }
  console.log(Foo.X)

  Also, the rule that requires converting numbers to a string currently only followed for 32-bit signed integers and non-finite numbers. This is done to avoid accidentally introducing a bug if esbuild's number-to-string operation doesn't exactly match the behavior of a real JavaScript VM. Currently esbuild's number-to-string constant folding is conservative for safety.

• Forbid definite assignment assertion operators on class methods

  In TypeScript, class methods can use the ? optional property operator but not the ! definite assignment assertion operator (while class fields can use both):

  class Foo {
    // These are valid TypeScript
    a?
    b!
    x?() {}
  
    // This is invalid TypeScript
    y!() {}
  }

  Previously esbuild incorrectly allowed the definite assignment assertion operator with class methods. This will no longer be allowed starting with this release.

v0.17.4

Compare Source

• Implement HTTP HEAD requests in serve mode (#​2851)

  Previously esbuild's serve mode only responded to HTTP GET requests. With this release, esbuild's serve mode will also respond to HTTP HEAD requests, which are just like HTTP GET requests except that the body of the response is omitted.

• Permit top-level await in dead code branches (#​2853)

  Adding top-level await to a file has a few consequences with esbuild:

  1. It causes esbuild to assume that the input module format is ESM, since top-level await is only syntactically valid in ESM. That prevents you from using module and exports for exports and also enables strict mode, which disables certain syntax and changes how function hoisting works (among other things).
  2. This will cause esbuild to fail the build if either top-level await isn't supported by your language target (e.g. it's not supported in ES2021) or if top-level await isn't supported by the chosen output format (e.g. it's not supported with CommonJS).
  3. Doing this will prevent you from using require() on this file or on any file that imports this file (even indirectly), since the require() function doesn't return a promise and so can't represent top-level await.

  This release relaxes these rules slightly: rules 2 and 3 will now no longer apply when esbuild has identified the code branch as dead code, such as when it's behind an if (false) check. This should make it possible to use esbuild to convert code into different output formats that only uses top-level await conditionally. This release does not relax rule 1. Top-level await will still cause esbuild to unconditionally consider the input module format to be ESM, even when the top-level await is in a dead code branch. This is necessary because whether the input format is ESM or not affects the whole file, not just the dead code branch.

• Fix entry points where the entire file name is the extension (#​2861)

  Previously if you passed esbuild an entry point where the file extension is the entire file name, esbuild would use the parent directory name to derive the name of the output file. For example, if you passed esbuild a file ./src/.ts then the output name would be src.js. This bug happened because esbuild first strips the file extension to get ./src/ and then joins the path with the working directory to get the absolute path (e.g. join("/working/dir", "./src/") gives /working/dir/src). However, the join operation also canonicalizes the path which strips the trailing /. Later esbuild uses the "base name" operation to extract the name of the output file. Since there is no trailing /, esbuild returns "src" as the base name instead of "", which causes esbuild to incorrectly include the directory name in the output file name. This release fixes this bug by deferring the stripping of the file extension until after all path manipulations have been completed. So now the file ./src/.ts will generate an output file named .js.

• Support replacing property access expressions with inject

  At a high level, this change means the inject feature can now replace all of the same kinds of names as the define feature. So inject is basically now a more powerful version of define, instead of previously only being able to do some of the things that define could do.

  Soem background is necessary to understand this change if you aren't already familiar with the inject feature. The inject feature lets you replace references to global variable with a shim. It works like this:

  1. Put the shim in its own file
  2. Export the shim as the name of the global variable you intend to replace
  3. Pass the file to esbuild using the inject feature

  For example, if you inject the following file using --inject:./injected.js:

  // injected.js
  let processShim = { cwd: () => '/' }
  export { processShim as process }

  Then esbuild will replace all references to process with the processShim variable, which will cause process.cwd() to return '/'. This feature is sort of abusing the ESM export alias syntax to specify the mapping of global variables to shims. But esbuild works this way because using this syntax for that purpose is convenient and terse.

  However, if you wanted to replace a property access expression, the process was more complicated and not as nice. You would have to:

  1. Put the shim in its own file
  2. Export the shim as some random name
  3. Pass the file to esbuild using the inject feature
  4. Use esbuild's define feature to map the property access expression to the random name you made in step 2

  For example, if you inject the following file using --inject:./injected2.js --define:process.cwd=someRandomName:

  // injected2.js
  let cwdShim = () => '/'
  export { cwdShim as someRandomName }

  Then esbuild will replace all references to process.cwd with the cwdShim variable, which will also cause process.cwd() to return '/' (but which this time will not mess with other references to process, which might be desirable).

  With this release, using the inject feature to replace a property access expression is now as simple as using it to replace an identifier. You can now use JavaScript's "arbitrary module namespace identifier names" feature to specify the property access expression directly using a string literal. For example, if you inject the following file using --inject:./injected3.js:

  // injected3.js
  let cwdShim = () => '/'
  export { cwdShim as 'process.cwd' }

  Then esbuild will now replace all references to process.cwd with the cwdShim variable, which will also cause process.cwd() to return '/' (but which will also not mess with other references to process).

  In addition to inserting a shim for a global variable that doesn't exist, another use case is replacing references to static methods on global objects with cached versions to both minify them better and to make access to them potentially faster. For example:

  // Injected file
  let cachedMin = Math.min
  let cachedMax = Math.max
  export {
    cachedMin as 'Math.min',
    cachedMax as 'Math.max',
  }
  
  // Original input
  function clampRGB(r, g, b) {
    return {
      r: Math.max(0, Math.min(1, r)),
      g: Math.max(0, Math.min(1, g)),
      b: Math.max(0, Math.min(1, b)),
    }
  }
  
  // Old output (with --minify)
  function clampRGB(a,t,m){return{r:Math.max(0,Math.min(1,a)),g:Math.max(0,Math.min(1,t)),b:Math.max(0,Math.min(1,m))}}
  
  // New output (with --minify)
  var a=Math.min,t=Math.max;function clampRGB(h,M,m){return{r:t(0,a(1,h)),g:t(0,a(1,M)),b:t(0,a(1,m))}}

v0.17.3

Compare Source

• Fix incorrect CSS minification for certain rules (#​2838)

  Certain rules such as @media could previously be minified incorrectly. Due to a typo in the duplicate rule checker, two known @-rules that share the same hash code were incorrectly considered to be equal. This problem was made worse by the rule hashing code considering two unknown declarations (such as CSS variables) to have the same hash code, which also isn't optimal from a performance perspective. Both of these issues have been fixed:

  /* Original input */
  @​media (prefers-color-scheme: dark) { body { --VAR-1: #​000; } }
  @​media (prefers-color-scheme: dark) { body { --VAR-2: #​000; } }
  
  /* Old output (with --minify) */
  @​media (prefers-color-scheme: dark){body{--VAR-2: #​000}}
  
  /* New output (with --minify) */
  @​media (prefers-color-scheme: dark){body{--VAR-1: #​000}}@​media (prefers-color-scheme: dark){body{--VAR-2: #​000}}

v0.17.2

Compare Source

• Add onDispose to the plugin API (#​2140, #​2205)

  If your plugin wants to perform some cleanup after it's no longer going to be used, you can now use the onDispose API to register a callback for cleanup-related tasks. For example, if a plugin starts a long-running child process then it may want to terminate that process when the plugin is discarded. Previously there was no way to do this. Here's an example:

  let examplePlugin = {
    name: 'example',
    setup(build) {
      build.onDispose(() => {
        console.log('This plugin is no longer used')
      })
    },
  }

  These onDispose callbacks will be called after every build() call regardless of whether the build failed or not as well as after the first dispose() call on a given build context.

v0.17.1

Compare Source

• Allow the TypeScript 5.0 const modifier in object type declarations (#​3021)

  The new TypeScript 5.0 const modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:

  interface Foo { <const T>(): T }
  type Bar = { new <const T>(): T }

• Implement preliminary lowering for CSS nesting (#​1945)

  Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!

  This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the :is() pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support :is() (e.g. Chrome 88+). You'll need to set esbuild's target to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a target which includes older browsers that don't support :is().

  The lowering transformation looks like this:

  /* Original input */
  a.btn {
    color: #​333;
    &:hover { color: #​444 }
    &:active { color: #​555 }
  }
  
  /* New output (with --target=chrome88) */
  a.btn {
    color: #​333;
  }
  a.btn:hover {
    color: #​444;
  }
  a.btn:active {
    color: #​555;
  }

  More complex cases may generate the :is() pseudo-class:

  /* Original input */
  div, p {
    .warning, .error {
      padding: 20px;
    }
  }
  
  /* New output (with --target=chrome88) */
  :is(div, p) :is(.warning, .error) {
    padding: 20px;
  }

  In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:

  ▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error]
  
      <stdin>:1:7:
        1 │ main { p { margin: auto } }
          │        ^
          ╵        :is(p)
  
    To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to
    prevent the rule from being parsed as a declaration.
  

  Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.

• Minification now removes unnecessary & CSS nesting selectors

  This release introduces the following CSS minification optimizations:

  /* Original input */
  a {
    font-weight: bold;
    & {
      color: blue;
    }
    & :hover {
      text-decoration: underline;
    }
  }
  
  /* Old output (with --minify) */
  a{font-weight:700;&{color:#​00f}& :hover{text-decoration:underline}}
  
  /* New output (with --minify) */
  a{font-weight:700;:hover{text-decoration:underline}color:#​00f}

• Minification now removes duplicates from CSS selector lists

  This release introduces the following CSS minification optimization:

  /* Original input */
  div, div { color: red }
  
  /* Old output (with --minify) */
  div,div{color:red}
  
  /* New output (with --minify) */
  div{color:red}

v0.17.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.16.0 or ~0.16.0. See npm's documentation about semver for more information.

At a high level, the breaking changes in this release fix some long-standing issues with the design of esbuild's incremental, watch, and serve APIs. This release also introduces some exciting new features such as live reloading. In detail:

• Move everything related to incremental builds to a new context API (#​1037, #​1606, #​2280, #​2418)

  This change removes the incremental and watch options as well as the serve() method, and introduces a new context() method. The context method takes the same arguments as the build() method but only validates its arguments and does not do an initial build. Instead, builds can be triggered using the rebuild(), watch(), and serve() methods on the returned context object. The new context API looks like this:

  // Create a context for incremental builds
  const context = await esbuild.context({
    entryPoints: ['app.ts'],
    bundle: true,
  })
  
  // Manually do an incremental build
  const result = await context.rebuild()
  
  // Enable watch mode
  await context.watch()
  
  // Enable serve mode
  await context.serve()
  
  // Dispose of the context
  context.dispose()

  The switch to the context API solves a major issue with the previous API which is that if the initial build fails, a promise is thrown in JavaScript which prevents you from accessing the returned result object. That prevented you from setting up long-running operations such as watch mode when the initial build contained errors. It also makes tearing down incremental builds simpler as there is now a single way to do it instead of three separate ways.

  In addition, this release also makes some subtle changes to how incremental builds work. Previously every call to rebuild() started a new build. If you weren't careful, then builds could actually overlap. This doesn't cause any problems with esbuild itself, but could potentially cause problems with plugins (esbuild doesn't even give you a way to identify which overlapping build a given plugin callback is running on). Overlapping builds also arguably aren't useful, or at least aren't useful enough to justify the confusion and complexity that they bring. With this release, there is now only ever a single active build per context. Calling rebuild() before the previous rebuild has finished now "merges" with the existing rebuild instead of starting a new build.

• Allow using watch and serve together (#​805, #​1650, #​2576)

  Previously it was not possible to use watch mode and serve mode together. The rationale was that watch mode is one way of automatically rebuilding your project and serve mode is another (since serve mode automatically rebuilds on every request). However, people want to combine these two features to make "live reloading" where the browser automatically reloads the page when files are changed on the file system.

  This release now allows you to use these two features together. You can only call the watch() and serve() APIs once each per context, but if you call them together on the same context then esbuild will automatically rebuild both when files on the file system are changed and when the server serves a request.

• Support "live reloading" through server-sent events (#​802)

  Server-sent events are a simple way to pass one-directional messages asynchronously from the server to the client. Serve mode now provides a /esbuild endpoint with an change event that triggers every time esbuild's output changes. So you can now implement simple "live reloading" (i.e. reloading the page when a file is edited and saved) like this:

  new EventSource('/esbuild').addEventListener('change', () => location.reload())

  The event payload is a JSON object with the following shape:

  interface ChangeEvent {
    added: string[]
    removed: string[]
    updated: string[]
  }

  This JSON should also enable more complex live reloading scenarios. For example, the following code hot-swaps changed CSS <link> tags in place without reloading the page (but still reloads when there are other types of changes):

  new EventSource('/esbuild').addEventListener('change', e => {
    const { added, removed, updated } = JSON.parse(e.data)
    if (!added.length && !removed.length && updated.length === 1) {
      for (const link of document.getElementsByTagName("link")) {
        const url = new URL(link.href)
        if (url.host === location.host && url.pathname === updated[0]) {
          const next = link.cloneNode()
          next.href = updated[0] + '?' + Math.random().toString(36).slice(2)
          next.onload = () => link.remove()
          link.parentNode.insertBefore(next, link.nextSibling)
          return
        }
      }
    }
    location.reload()
  })

  Implementing live reloading like this has a few known caveats:

  • These events only trigger when esbuild's output changes. They do not trigger when files unrelated to the build being watched are changed. If your HTML file references other files that esbuild doesn't know about and those files are changed, you can either manually reload the page or you can implement your own live reloading infrastructure instead of using esbuild's built-in behavior.

  • The EventSource API is supposed to automatically reconnect for you. However, there's a bug in Firefox that breaks this if the server is ever temporarily unreachable: https://bugzilla.mozilla.org/show_bug.cgi?id=1809332. Workarounds are to use any other browser, to manually reload the page if this happens, or to write more complicated code that manually closes and re-creates the EventSource object if there is a connection error. I'm hopeful that this bug will be fixed.

  • Browser vendors have decided to not implement HTTP/2 without TLS. This means that each /esbuild event source will take up one of your precious 6 simultaneous per-domain HTTP/1.1 connections. So if you open more than six HTTP tabs that use this live-reloading technique, you will be unable to use live reloading in some of those tabs (and other things will likely also break). The workaround is to enable HTTPS, which is now possible to do in esbuild itself (see below).

• Add built-in support for HTTPS (#​2169)

  You can now tell esbuild's built-in development server to use HTTPS instead of HTTP. This is sometimes necessary because browser vendors have started making modern web features unavailable to HTTP websites. Previously you had to put a proxy in front of esbuild to enable HTTPS since esbuild's development server only supported HTTP. But with this release, you can now enable HTTPS with esbuild without an additional proxy.

  To enable HTTPS with esbuild:

  1. Generate a self-signed certificate. There are many ways to do this. Here's one way, assuming you have openssl installed:

     openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 9999 -nodes -subj /CN=127.0.0.1
     

  2. Add --keyfile=key.pem and --certfile=cert.pem to your esbuild development server command

  3. Click past the scary warning in your browser when you load your page

  If you have more complex needs than this, you can still put a proxy in front of esbuild and use that for HTTPS instead. Note that if you see the message "Client sent an HTTP request to an HTTPS server" when you load your page, then you are using the incorrect protocol. Replace http:// with https:// in your browser's URL bar.

  Keep in mind that esbuild's HTTPS support has nothing to do with security. The only reason esbuild now supports HTTPS is because browsers have made it impossible to do local development with certain modern web features without jumping through these extra hoops. Please do not use esbuild's development server for anything that needs to be secure. It's only intended for local development and no considerations have been made for production environments whatsoever.

• Better support copying index.html into the output directory (#​621, #​1771)

  Right now esbuild only supports JavaScript and CSS as first-class content types. Previously this meant that if you were building a website with a HTML file, a JavaScript file, and a CSS file, you could use esbuild to build the JavaScript file and the CSS file into the output directory but not to copy the HTML file into the output directory. You needed a separate cp command for that.

  Or so I thought. It turns out that the copy loader added in version 0.14.44 of esbuild is sufficient to have esbuild copy the HTML file into the output directory as well. You can add something like index.html --loader:.html=copy and esbuild will copy index.html into the output directory for you. The benefits of this are a) you don't need a separate cp command and b) the index.html file will automatically be re-copied when esbuild is in watch mode and the contents of index.html are edited. This also goes for other non-HTML file types that you might want to copy.

  This pretty much already worked. The one thing that didn't work was that esbuild's built-in development server previously only supported implicitly loading index.html (e.g. loading /about/index.html when you visit /about/) when index.html existed on the file system. Previously esbuild didn't support implicitly loading index.html if it was a build result. That bug has been fixed with this release so it should now be practical to use the copy loader to do this.

• Fix onEnd not being called in serve mode (#​1384)

  Previous releases had a bug where plugin onEnd callbacks weren't called when using the top-level serve() API. This API no longer exists and the internals have been reimplemented such that onEnd callbacks should now always be called at the end of every build.

• Incremental builds now write out build results differently (#​2104)

  Previously build results were always written out after every build. However, this could cause the output directory to fill up with files from old builds if code splitting was enabled, since the file names for code splitting chunks contain content hashes and old files were not deleted.

  With this release, incremental builds in esbuild will now delete old output files from previous builds that are no longer relevant. Subsequent incremental builds will also no longer overwrite output files whose contents haven't changed since the previous incremental build.

• The onRebuild watch mode callback was removed (#​980, #​2499)

  Previously watch mode accepted an onRebuild callback which was called whenever watch mode rebuilt something. This was not great in practice because if you are running code after a build, you likely want that code to run after every build, not just after the second and subsequent builds. This release removes option to provide an onRebuild callback. You can create a plugin with an onEnd callback instead. The onEnd plugin API already exists, and is a way to run some code after every build.

• You can now return errors from onEnd (#​2625)

  It's now possible to add additional build errors and/or warnings to the current build from within your onEnd callback by returning them in an array. This is identical to how the onStart callback already works. The evaluation of onEnd callbacks have been moved around a bit internally to make this possible.

  Note that the build will only fail (i.e. reject the promise) if the additional errors are returned from onEnd. Adding additional errors to the result object that's passed to onEnd won't affect esbuild's behavior at all.

• Print URLs and ports from

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Diff Output:

Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
latest: Pulling from sam/build-python3.9
2a2cc0d36b60: Pulling fs layer
e09d761c851a: Pulling fs layer
0a7d5b36cadf: Pulling fs layer
072730bdc14d: Pulling fs layer
b546b14c8cf0: Pulling fs layer
e046c1efb9ee: Pulling fs layer
c4c847a941a2: Pulling fs layer
c5649394f0aa: Pulling fs layer
2a6038f4ed7c: Pulling fs layer
f6f344e1421e: Pulling fs layer
33b8dc70253c: Pulling fs layer
c4c847a941a2: Waiting
c5649394f0aa: Waiting
2a6038f4ed7c: Waiting
f6f344e1421e: Waiting
33b8dc70253c: Waiting
072730bdc14d: Waiting
b546b14c8cf0: Waiting
e046c1efb9ee: Waiting
0a7d5b36cadf: Verifying Checksum
0a7d5b36cadf: Download complete
e09d761c851a: Verifying Checksum
e09d761c851a: Download complete
072730bdc14d: Verifying Checksum
072730bdc14d: Download complete
e046c1efb9ee: Verifying Checksum
e046c1efb9ee: Download complete
b546b14c8cf0: Verifying Checksum
b546b14c8cf0: Download complete
2a2cc0d36b60: Verifying Checksum
2a2cc0d36b60: Download complete
c5649394f0aa: Verifying Checksum
c5649394f0aa: Download complete
2a6038f4ed7c: Verifying Checksum
2a6038f4ed7c: Download complete
f6f344e1421e: Verifying Checksum
f6f344e1421e: Download complete
33b8dc70253c: Verifying Checksum
33b8dc70253c: Download complete
c4c847a941a2: Verifying Checksum
c4c847a941a2: Download complete
2a2cc0d36b60: Pull complete
e09d761c851a: Pull complete
0a7d5b36cadf: Pull complete
072730bdc14d: Pull complete
b546b14c8cf0: Pull complete
e046c1efb9ee: Pull complete
c4c847a941a2: Pull complete
c5649394f0aa: Pull complete
2a6038f4ed7c: Pull complete
f6f344e1421e: Pull complete
33b8dc70253c: Pull complete
Digest: sha256:a3cac68642ed34bda436999f02b40522f64fe5ef218cb4f9037b82cbee56162d
Status: Downloaded newer image for public.ecr.aws/sam/build-python3.9:latest
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Running in 1af17bf2bcd9
Removing intermediate container 1af17bf2bcd9
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Running in 53d4484a701f
Removing intermediate container 53d4484a701f
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Running in 6940500be79c
Removing intermediate container 6940500be79c
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Running in 1764b76953ee
Requirement already satisfied: pip in /var/lang/lib/python3.9/site-packages (22.0.4)
Collecting pip
  Downloading pip-23.0.1-py3-none-any.whl (2.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 36.3 MB/s eta 0:00:00
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 22.0.4
    Uninstalling pip-22.0.4:
      Successfully uninstalled pip-22.0.4
Successfully installed pip-23.0.1
�[91mWARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
�[0mRemoving intermediate container 1764b76953ee
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Running in 29ca8c2854b8
Collecting pipenv==2022.4.8
  Downloading pipenv-2022.4.8-py2.py3-none-any.whl (3.6 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.6/3.6 MB 52.9 MB/s eta 0:00:00
Collecting poetry
  Downloading poetry-1.4.1-py3-none-any.whl (222 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 222.3/222.3 kB 52.6 MB/s eta 0:00:00
Collecting virtualenv-clone>=0.2.5
  Downloading virtualenv_clone-0.5.7-py3-none-any.whl (6.6 kB)
Collecting certifi
  Downloading certifi-2022.12.7-py3-none-any.whl (155 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 155.3/155.3 kB 47.7 MB/s eta 0:00:00
Requirement already satisfied: setuptools>=36.2.1 in /var/lang/lib/python3.9/site-packages (from pipenv==2022.4.8) (58.1.0)
Requirement already satisfied: pip>=18.0 in /var/lang/lib/python3.9/site-packages (from pipenv==2022.4.8) (23.0.1)
Collecting virtualenv
  Downloading virtualenv-20.21.0-py3-none-any.whl (8.7 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.7/8.7 MB 119.2 MB/s eta 0:00:00
Collecting platformdirs<3.0.0,>=2.5.2
  Downloading platformdirs-2.6.2-py3-none-any.whl (14 kB)
Collecting shellingham<2.0,>=1.5
  Downloading shellingham-1.5.0.post1-py2.py3-none-any.whl (9.4 kB)
Collecting poetry-plugin-export<2.0.0,>=1.3.0
  Downloading poetry_plugin_export-1.3.0-py3-none-any.whl (10 kB)
Collecting installer<0.8.0,>=0.7.0
  Downloading installer-0.7.0-py3-none-any.whl (453 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 453.8/453.8 kB 77.3 MB/s eta 0:00:00
Collecting urllib3<2.0.0,>=1.26.0
  Downloading urllib3-1.26.15-py2.py3-none-any.whl (140 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 140.9/140.9 kB 45.4 MB/s eta 0:00:00
Collecting cleo<3.0.0,>=2.0.0
  Downloading cleo-2.0.1-py3-none-any.whl (77 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 77.3/77.3 kB 26.1 MB/s eta 0:00:00
Collecting pexpect<5.0.0,>=4.7.0
  Downloading pexpect-4.8.0-py2.py3-none-any.whl (59 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 59.0/59.0 kB 20.5 MB/s eta 0:00:00
Collecting requests-toolbelt<0.11.0,>=0.9.1
  Downloading requests_toolbelt-0.10.1-py2.py3-none-any.whl (54 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 54.5/54.5 kB 16.0 MB/s eta 0:00:00
Collecting requests<3.0,>=2.18
  Downloading requests-2.28.2-py3-none-any.whl (62 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.8/62.8 kB 18.6 MB/s eta 0:00:00
Collecting crashtest<0.5.0,>=0.4.1
  Downloading crashtest-0.4.1-py3-none-any.whl (7.6 kB)
Collecting importlib-metadata>=4.4
  Downloading importlib_metadata-6.1.0-py3-none-any.whl (21 kB)
Collecting html5lib<2.0,>=1.0
  Downloading html5lib-1.1-py2.py3-none-any.whl (112 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 112.2/112.2 kB 41.3 MB/s eta 0:00:00
Collecting pkginfo<2.0.0,>=1.9.4
  Downloading pkginfo-1.9.6-py3-none-any.whl (30 kB)
Collecting filelock<4.0.0,>=3.8.0
  Downloading filelock-3.10.7-py3-none-any.whl (10 kB)
Collecting build<0.11.0,>=0.10.0
  Downloading build-0.10.0-py3-none-any.whl (17 kB)
Collecting tomlkit!=0.11.2,!=0.11.3,<1.0.0,>=0.11.1
  Downloading tomlkit-0.11.7-py3-none-any.whl (35 kB)
Collecting trove-classifiers>=2022.5.19
  Downloading trove_classifiers-2023.3.9-py3-none-any.whl (13 kB)
Collecting tomli<3.0.0,>=2.0.1
  Downloading tomli-2.0.1-py3-none-any.whl (12 kB)
Collecting lockfile<0.13.0,>=0.12.2
  Downloading lockfile-0.12.2-py2.py3-none-any.whl (13 kB)
Collecting poetry-core==1.5.2
  Downloading poetry_core-1.5.2-py3-none-any.whl (465 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 465.2/465.2 kB 84.3 MB/s eta 0:00:00
Collecting dulwich<0.22.0,>=0.21.2
  Downloading dulwich-0.21.3-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (505 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 505.9/505.9 kB 92.5 MB/s eta 0:00:00
Collecting pyproject-hooks<2.0.0,>=1.0.0
  Downloading pyproject_hooks-1.0.0-py3-none-any.whl (9.3 kB)
Collecting packaging>=20.4
  Downloading packaging-23.0-py3-none-any.whl (42 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 42.7/42.7 kB 14.9 MB/s eta 0:00:00
Collecting keyring<24.0.0,>=23.9.0
  Downloading keyring-23.13.1-py3-none-any.whl (37 kB)
Collecting cachecontrol[filecache]<0.13.0,>=0.12.9
  Downloading CacheControl-0.12.11-py2.py3-none-any.whl (21 kB)
Collecting jsonschema<5.0.0,>=4.10.0
  Downloading jsonschema-4.17.3-py3-none-any.whl (90 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 90.4/90.4 kB 31.8 MB/s eta 0:00:00
Collecting msgpack>=0.5.2
  Downloading msgpack-1.0.5-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (322 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 322.3/322.3 kB 68.2 MB/s eta 0:00:00
Collecting rapidfuzz<3.0.0,>=2.2.0
  Downloading rapidfuzz-2.13.7-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (2.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.2/2.2 MB 122.5 MB/s eta 0:00:00
Collecting webencodings
  Downloading webencodings-0.5.1-py2.py3-none-any.whl (11 kB)
Collecting six>=1.9
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting zipp>=0.5
  Downloading zipp-3.15.0-py3-none-any.whl (6.8 kB)
Collecting attrs>=17.4.0
  Downloading attrs-22.2.0-py3-none-any.whl (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.0/60.0 kB 15.2 MB/s eta 0:00:00
Collecting pyrsistent!=0.17.0,!=0.17.1,!=0.17.2,>=0.14.0
  Downloading pyrsistent-0.19.3-py3-none-any.whl (57 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 57.5/57.5 kB 9.0 MB/s eta 0:00:00
Collecting jeepney>=0.4.2
  Downloading jeepney-0.8.0-py3-none-any.whl (48 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 48.4/48.4 kB 14.8 MB/s eta 0:00:00
Collecting SecretStorage>=3.2
  Downloading SecretStorage-3.3.3-py3-none-any.whl (15 kB)
Collecting jaraco.classes
  Downloading jaraco.classes-3.2.3-py3-none-any.whl (6.0 kB)
Collecting ptyprocess>=0.5
  Downloading ptyprocess-0.7.0-py2.py3-none-any.whl (13 kB)
Collecting idna<4,>=2.5
  Downloading idna-3.4-py3-none-any.whl (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.5/61.5 kB 20.3 MB/s eta 0:00:00
Collecting charset-normalizer<4,>=2
  Downloading charset_normalizer-3.1.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (199 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 199.2/199.2 kB 56.0 MB/s eta 0:00:00
Collecting distlib<1,>=0.3.6
  Downloading distlib-0.3.6-py2.py3-none-any.whl (468 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 468.5/468.5 kB 93.4 MB/s eta 0:00:00
Collecting cryptography>=2.0
  Downloading cryptography-40.0.1-cp36-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.7 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.7/3.7 MB 122.4 MB/s eta 0:00:00
Collecting more-itertools
  Downloading more_itertools-9.1.0-py3-none-any.whl (54 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 54.2/54.2 kB 15.0 MB/s eta 0:00:00
Collecting cffi>=1.12
  Downloading cffi-1.15.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (441 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 441.2/441.2 kB 80.8 MB/s eta 0:00:00
Collecting pycparser
  Downloading pycparser-2.21-py2.py3-none-any.whl (118 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 118.7/118.7 kB 43.9 MB/s eta 0:00:00
Installing collected packages: webencodings, trove-classifiers, ptyprocess, msgpack, lockfile, distlib, zipp, virtualenv-clone, urllib3, tomlkit, tomli, six, shellingham, rapidfuzz, pyrsistent, pycparser, poetry-core, platformdirs, pkginfo, pexpect, packaging, more-itertools, jeepney, installer, idna, filelock, crashtest, charset-normalizer, certifi, attrs, virtualenv, requests, pyproject-hooks, jsonschema, jaraco.classes, importlib-metadata, html5lib, dulwich, cleo, cffi, requests-toolbelt, pipenv, cryptography, cachecontrol, build, SecretStorage, keyring, poetry-plugin-export, poetry
Successfully installed SecretStorage-3.3.3 attrs-22.2.0 build-0.10.0 cachecontrol-0.12.11 certifi-2022.12.7 cffi-1.15.1 charset-normalizer-3.1.0 cleo-2.0.1 crashtest-0.4.1 cryptography-40.0.1 distlib-0.3.6 dulwich-0.21.3 filelock-3.10.7 html5lib-1.1 idna-3.4 importlib-metadata-6.1.0 installer-0.7.0 jaraco.classes-3.2.3 jeepney-0.8.0 jsonschema-4.17.3 keyring-23.13.1 lockfile-0.12.2 more-itertools-9.1.0 msgpack-1.0.5 packaging-23.0 pexpect-4.8.0 pipenv-2022.4.8 pkginfo-1.9.6 platformdirs-2.6.2 poetry-1.4.1 poetry-core-1.5.2 poetry-plugin-export-1.3.0 ptyprocess-0.7.0 pycparser-2.21 pyproject-hooks-1.0.0 pyrsistent-0.19.3 rapidfuzz-2.13.7 requests-2.28.2 requests-toolbelt-0.10.1 shellingham-1.5.0.post1 six-1.16.0 tomli-2.0.1 tomlkit-0.11.7 trove-classifiers-2023.3.9 urllib3-1.26.15 virtualenv-20.21.0 virtualenv-clone-0.5.7 webencodings-0.5.1 zipp-3.15.0
�[91mWARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
�[0mRemoving intermediate container 29ca8c2854b8
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Running in e7d0d379ec48
Removing intermediate container e7d0d379ec48
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset persistence/syllabus-datapipeline/scraper-base-function/base-function/Code/Stage...
WARNING: The directory '/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Collecting lxml
  Downloading lxml-4.9.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl (7.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.1/7.1 MB 99.5 MB/s eta 0:00:00
Installing collected packages: lxml
Successfully installed lxml-4.9.2
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
[WARNING] aws-cdk-lib.aws_stepfunctions_tasks.LambdaInvokeProps#qualifier is deprecated.
  pass a Version or Alias object as lambdaFunction instead
  This API will be removed in the next major release.
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset persistence/syllabus-sync/syllabus-update-function/update-syllabus/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/cognito-endpoint/presign-up-handle/base-function/Code/Stage...
[WARNING] aws-cdk-lib.aws_cognito.UserPoolIdentityProviderGoogleProps#clientSecret is deprecated.
  use clientSecretValue instead
  This API will be removed in the next major release.
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/syllabus-api/syllabus-function/get-course/Code/Stage...
WARNING: The directory '/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Collecting lxml
  Downloading lxml-4.9.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl (7.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.1/7.1 MB 96.7 MB/s eta 0:00:00
Installing collected packages: lxml
Successfully installed lxml-4.9.2
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/syllabus-api/syllabus-function/post-book/Code/Stage...
WARNING: The directory '/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Collecting aiohttp
  Downloading aiohttp-3.8.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (1.0 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.0/1.0 MB 25.4 MB/s eta 0:00:00
Collecting frozenlist>=1.1.1
  Downloading frozenlist-1.3.3-cp39-cp39-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl (158 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 158.8/158.8 kB 257.8 MB/s eta 0:00:00
Collecting attrs>=17.3.0
  Downloading attrs-22.2.0-py3-none-any.whl (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.0/60.0 kB 227.3 MB/s eta 0:00:00
Collecting charset-normalizer<4.0,>=2.0
  Downloading charset_normalizer-3.1.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (199 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 199.2/199.2 kB 280.0 MB/s eta 0:00:00
Collecting yarl<2.0,>=1.0
  Downloading yarl-1.8.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (264 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 264.6/264.6 kB 289.8 MB/s eta 0:00:00
Collecting multidict<7.0,>=4.5
  Downloading multidict-6.0.4-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (114 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 114.2/114.2 kB 253.6 MB/s eta 0:00:00
Collecting async-timeout<5.0,>=4.0.0a3
  Downloading async_timeout-4.0.2-py3-none-any.whl (5.8 kB)
Collecting aiosignal>=1.1.2
  Downloading aiosignal-1.3.1-py3-none-any.whl (7.6 kB)
Collecting idna>=2.0
  Downloading idna-3.4-py3-none-any.whl (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.5/61.5 kB 225.5 MB/s eta 0:00:00
Installing collected packages: multidict, idna, frozenlist, charset-normalizer, attrs, async-timeout, yarl, aiosignal, aiohttp
Successfully installed aiohttp-3.8.4 aiosignal-1.3.1 async-timeout-4.0.2 attrs-22.2.0 charset-normalizer-3.1.0 frozenlist-1.3.3 idna-3.4 multidict-6.0.4 yarl-1.8.2
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/course-reviews-api/crud-functions/get-reviews/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/course-reviews-api/crud-functions/post-review/Code/Stage...
WARNING: The directory '/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Collecting google-cloud-translate
  Downloading google_cloud_translate-3.11.1-py2.py3-none-any.whl (128 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 128.4/128.4 kB 7.2 MB/s eta 0:00:00
Collecting google-cloud-core<3.0.0dev,>=1.3.0
  Downloading google_cloud_core-2.3.2-py2.py3-none-any.whl (29 kB)
Collecting proto-plus<2.0.0dev,>=1.22.0
  Downloading proto_plus-1.22.2-py3-none-any.whl (47 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 47.9/47.9 kB 214.9 MB/s eta 0:00:00
Collecting protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5
  Downloading protobuf-4.22.1-cp37-abi3-manylinux2014_x86_64.whl (302 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 302.4/302.4 kB 31.0 MB/s eta 0:00:00
Collecting google-api-core[grpc]!=2.0.*,!=2.1.*,!=2.10.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,!=2.9.*,<3.0.0dev,>=1.34.0
  Downloading google_api_core-2.11.0-py3-none-any.whl (120 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 120.3/120.3 kB 259.3 MB/s eta 0:00:00
Collecting requests<3.0.0dev,>=2.18.0
  Downloading requests-2.28.2-py3-none-any.whl (62 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.8/62.8 kB 218.2 MB/s eta 0:00:00
Collecting googleapis-common-protos<2.0dev,>=1.56.2
  Downloading googleapis_common_protos-1.59.0-py2.py3-none-any.whl (223 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 223.6/223.6 kB 197.7 MB/s eta 0:00:00
Collecting google-auth<3.0dev,>=2.14.1
  Downloading google_auth-2.16.3-py2.py3-none-any.whl (177 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 177.5/177.5 kB 273.9 MB/s eta 0:00:00
Collecting grpcio-status<2.0dev,>=1.33.2
  Downloading grpcio_status-1.53.0-py3-none-any.whl (5.1 kB)
Collecting grpcio<2.0dev,>=1.33.2
  Downloading grpcio-1.53.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.0 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.0/5.0 MB 80.7 MB/s eta 0:00:00
Collecting six>=1.9.0
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting pyasn1-modules>=0.2.1
  Downloading pyasn1_modules-0.2.8-py2.py3-none-any.whl (155 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 155.3/155.3 kB 262.4 MB/s eta 0:00:00
Collecting cachetools<6.0,>=2.0.0
  Downloading cachetools-5.3.0-py3-none-any.whl (9.3 kB)
Collecting rsa<5,>=3.1.4
  Downloading rsa-4.9-py3-none-any.whl (34 kB)
Collecting charset-normalizer<4,>=2
  Downloading charset_normalizer-3.1.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (199 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 199.2/199.2 kB 258.5 MB/s eta 0:00:00
Collecting idna<4,>=2.5
  Downloading idna-3.4-py3-none-any.whl (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.5/61.5 kB 215.9 MB/s eta 0:00:00
Collecting urllib3<1.27,>=1.21.1
  Downloading urllib3-1.26.15-py2.py3-none-any.whl (140 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 140.9/140.9 kB 271.2 MB/s eta 0:00:00
Collecting certifi>=2017.4.17
  Downloading certifi-2022.12.7-py3-none-any.whl (155 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 155.3/155.3 kB 273.2 MB/s eta 0:00:00
Collecting pyasn1<0.5.0,>=0.4.6
  Downloading pyasn1-0.4.8-py2.py3-none-any.whl (77 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 77.1/77.1 kB 219.1 MB/s eta 0:00:00
Installing collected packages: pyasn1, urllib3, six, rsa, pyasn1-modules, protobuf, idna, grpcio, charset-normalizer, certifi, cachetools, requests, proto-plus, googleapis-common-protos, google-auth, grpcio-status, google-api-core, google-cloud-core, google-cloud-translate
Successfully installed cachetools-5.3.0 certifi-2022.12.7 charset-normalizer-3.1.0 google-api-core-2.11.0 google-auth-2.16.3 google-cloud-core-2.3.2 google-cloud-translate-3.11.1 googleapis-common-protos-1.59.0 grpcio-1.53.0 grpcio-status-1.53.0 idna-3.4 proto-plus-1.22.2 protobuf-4.22.1 pyasn1-0.4.8 pyasn1-modules-0.2.8 requests-2.28.2 rsa-4.9 six-1.16.0 urllib3-1.26.15
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/course-reviews-api/crud-functions/patch-review/Code/Stage...
WARNING: The directory '/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Collecting google-cloud-translate
  Downloading google_cloud_translate-3.11.1-py2.py3-none-any.whl (128 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 128.4/128.4 kB 7.8 MB/s eta 0:00:00
Collecting protobuf!=3.20.0,!=3.20.1,!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<5.0.0dev,>=3.19.5
  Downloading protobuf-4.22.1-cp37-abi3-manylinux2014_x86_64.whl (302 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 302.4/302.4 kB 32.0 MB/s eta 0:00:00
Collecting proto-plus<2.0.0dev,>=1.22.0
  Downloading proto_plus-1.22.2-py3-none-any.whl (47 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 47.9/47.9 kB 224.3 MB/s eta 0:00:00
Collecting google-api-core[grpc]!=2.0.*,!=2.1.*,!=2.10.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,!=2.9.*,<3.0.0dev,>=1.34.0
  Downloading google_api_core-2.11.0-py3-none-any.whl (120 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 120.3/120.3 kB 267.3 MB/s eta 0:00:00
Collecting google-cloud-core<3.0.0dev,>=1.3.0
  Downloading google_cloud_core-2.3.2-py2.py3-none-any.whl (29 kB)
Collecting requests<3.0.0dev,>=2.18.0
  Downloading requests-2.28.2-py3-none-any.whl (62 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.8/62.8 kB 233.8 MB/s eta 0:00:00
Collecting google-auth<3.0dev,>=2.14.1
  Downloading google_auth-2.16.3-py2.py3-none-any.whl (177 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 177.5/177.5 kB 267.5 MB/s eta 0:00:00
Collecting googleapis-common-protos<2.0dev,>=1.56.2
  Downloading googleapis_common_protos-1.59.0-py2.py3-none-any.whl (223 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 223.6/223.6 kB 168.0 MB/s eta 0:00:00
Collecting grpcio-status<2.0dev,>=1.33.2
  Downloading grpcio_status-1.53.0-py3-none-any.whl (5.1 kB)
Collecting grpcio<2.0dev,>=1.33.2
  Downloading grpcio-1.53.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (5.0 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.0/5.0 MB 155.4 MB/s eta 0:00:00
Collecting six>=1.9.0
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting pyasn1-modules>=0.2.1
  Downloading pyasn1_modules-0.2.8-py2.py3-none-any.whl (155 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 155.3/155.3 kB 254.9 MB/s eta 0:00:00
Collecting rsa<5,>=3.1.4
  Downloading rsa-4.9-py3-none-any.whl (34 kB)
Collecting cachetools<6.0,>=2.0.0
  Downloading cachetools-5.3.0-py3-none-any.whl (9.3 kB)
Collecting urllib3<1.27,>=1.21.1
  Downloading urllib3-1.26.15-py2.py3-none-any.whl (140 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 140.9/140.9 kB 253.0 MB/s eta 0:00:00
Collecting charset-normalizer<4,>=2
  Downloading charset_normalizer-3.1.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (199 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 199.2/199.2 kB 277.4 MB/s eta 0:00:00
Collecting idna<4,>=2.5
  Downloading idna-3.4-py3-none-any.whl (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.5/61.5 kB 228.1 MB/s eta 0:00:00
Collecting certifi>=2017.4.17
  Downloading certifi-2022.12.7-py3-none-any.whl (155 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 155.3/155.3 kB 260.2 MB/s eta 0:00:00
Collecting pyasn1<0.5.0,>=0.4.6
  Downloading pyasn1-0.4.8-py2.py3-none-any.whl (77 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 77.1/77.1 kB 240.4 MB/s eta 0:00:00
Installing collected packages: pyasn1, urllib3, six, rsa, pyasn1-modules, protobuf, idna, grpcio, charset-normalizer, certifi, cachetools, requests, proto-plus, googleapis-common-protos, google-auth, grpcio-status, google-api-core, google-cloud-core, google-cloud-translate
Successfully installed cachetools-5.3.0 certifi-2022.12.7 charset-normalizer-3.1.0 google-api-core-2.11.0 google-auth-2.16.3 google-cloud-core-2.3.2 google-cloud-translate-3.11.1 googleapis-common-protos-1.59.0 grpcio-1.53.0 grpcio-status-1.53.0 idna-3.4 proto-plus-1.22.2 protobuf-4.22.1 pyasn1-0.4.8 pyasn1-modules-0.2.8 requests-2.28.2 rsa-4.9 six-1.16.0 urllib3-1.26.15
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/course-reviews-api/crud-functions/delete-review/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/timetable-api/crud-functions/get-timetable/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/timetable-api/crud-functions/post-timetable/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/timetable-api/crud-functions/patch-timetable/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/timetable-api/crud-functions/put-timetable/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/thread-api/crud-functions/get-all-threads/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/thread-api/crud-functions/get-board-threads/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/thread-api/crud-functions/get-single-thread/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/thread-api/crud-functions/post-thread/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/thread-api/crud-functions/patch-thread/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/thread-api/crud-functions/delete-thread/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/comment-api/crud-functions/get-comment/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/comment-api/crud-functions/post-comment/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/comment-api/crud-functions/patch-comment/Code/Stage...
Sending build context to Docker daemon  57.34kB

Step 1/8 : ARG IMAGE=public.ecr.aws/sam/build-python3.7
Step 2/8 : FROM $IMAGE
 ---> 47a0b9927266
Step 3/8 : ARG PIP_INDEX_URL
 ---> Using cache
 ---> f014ea726729
Step 4/8 : ARG PIP_EXTRA_INDEX_URL
 ---> Using cache
 ---> dbaf75b36119
Step 5/8 : ARG HTTPS_PROXY
 ---> Using cache
 ---> ead5f3ee3136
Step 6/8 : RUN pip install --upgrade pip
 ---> Using cache
 ---> 2b959956f98a
Step 7/8 : RUN pip install pipenv==2022.4.8 poetry
 ---> Using cache
 ---> bc8737331eee
Step 8/8 : CMD [ "python" ]
 ---> Using cache
 ---> 0d5b81346226
Successfully built 0d5b81346226
Successfully tagged cdk-d1b04ed5a8dae0e10f922ff08378b1cb8079ff43bb7f4094e74e0046b52dbc8e:latest
Bundling asset business/rest-api-endpoint/comment-api/crud-functions/delete-comment/Code/Stage...
Bundling asset admin/build-notifier/subscriber-function/base-function/Code/Stage...

  ...6e39637ac75645a9825daad87e587044496ece63c533f75d565aca4d0/index.js  1.9kb

⚡ Done in 3ms
Bundling asset admin/scraper-notifier/subscriber-function/base-function/Code/Stage...

  ...02bf02427a2fa68dee3b8b6c0786254297368e2c741ef51623e605cc4/index.js  1.6kb

⚡ Done in 2ms
Stack persistence
There were no differences
Stack wt-hosted-zone
There were no differences
Stack business
Resources
[-] AWS::ApiGateway::Deployment restapiendpointdevdeployment6E7C4E8Af416173bd8b9a4582a134bcc4f869801 destroy
[+] AWS::ApiGateway::Deployment rest-api-endpoint/dev-deployment restapiendpointdevdeployment6E7C4E8A0a55e09869bf651f2c5bc75712fea246 
[~] AWS::ApiGateway::Stage rest-api-endpoint/dev-stage restapiendpointdevstage0CDF6AEB 
 └─ [~] DeploymentId
     └─ [~] .Ref:
         ├─ [-] restapiendpointdevdeployment6E7C4E8Af416173bd8b9a4582a134bcc4f869801
         └─ [+] restapiendpointdevdeployment6E7C4E8A0a55e09869bf651f2c5bc75712fea246

Stack presentation
IAM Statement Changes
┌───┬────────────────────────────────────────────────┬────────┬────────────────┬───────────────────────────────┬───────────┐
│   │ Resource                                       │ Effect │ Action         │ Principal                     │ Condition │
├───┼────────────────────────────────────────────────┼────────┼────────────────┼───────────────────────────────┼───────────┤
│ + │ ${amplify-monorepo-web-app/forum-app/Role.Arn} │ Allow  │ sts:AssumeRole │ Service:amplify.amazonaws.com │           │
└───┴────────────────────────────────────────────────┴────────┴────────────────┴───────────────────────────────┴───────────┘
(NOTE: There may be security-related changes not in this list. See https://github.com/aws/aws-cdk/issues/1299)

Resources
[+] AWS::IAM::Role amplify-monorepo-web-app/forum-app/Role amplifymonorepowebappforumappRole928214C4 
[+] AWS::Amplify::App amplify-monorepo-web-app/forum-app amplifymonorepowebappforumapp01FF34A3 
[+] AWS::Amplify::Branch amplify-monorepo-web-app/forum-app/master amplifymonorepowebappforumappmaster2199E537 
[+] AWS::Amplify::Branch amplify-monorepo-web-app/forum-app/dev amplifymonorepowebappforumappdev56A934B7 
[~] AWS::Amplify::App amplify-monorepo-web-app/root-app amplifymonorepowebapprootapp72CC35EB 
 ├─ [~] CustomRules
 │   └─ @@ -57,6 +57,25 @@
 │      [ ]   }
 │      [ ] },
 │      [ ] {
 │      [+]   "Source": "/forum/<*>",
 │      [+]   "Status": "200",
 │      [+]   "Target": {
 │      [+]     "Fn::Join": [
 │      [+]       "",
 │      [+]       [
 │      [+]         "https://master.",
 │      [+]         {
 │      [+]           "Fn::GetAtt": [
 │      [+]             "amplifymonorepowebappforumapp01FF34A3",
 │      [+]             "DefaultDomain"
 │      [+]           ]
 │      [+]         },
 │      [+]         "/<*>"
 │      [+]       ]
 │      [+]     ]
 │      [+]   }
 │      [+] },
 │      [+] {
 │      [ ]   "Source": "https://www.wasedatime.com",
 │      [ ]   "Status": "301",
 │      [ ]   "Target": "https://wasedatime.com"
 └─ [~] EnvironmentVariables
     └─ @@ -66,5 +66,14 @@
        [ ]         "DefaultDomain"
        [ ]       ]
        [ ]     }
        [+]   },
        [+]   {
        [+]     "Name": "MF_FORUM_DOMAIN",
        [+]     "Value": {
        [+]       "Fn::GetAtt": [
        [+]         "amplifymonorepowebappforumapp01FF34A3",
        [+]         "DefaultDomain"
        [+]       ]
        [+]     }
        [ ]   }
        [ ] ]

Outputs
[+] Output Exports/Output{"Fn::GetAtt":["amplifymonorepowebappforumapp01FF34A3","AppId"]} ExportsOutputFnGetAttamplifymonorepowebappforumapp01FF34A3AppId9A2F1BBF: {"Value":{"Fn::GetAtt":["amplifymonorepowebappforumapp01FF34A3","AppId"]},"Export":{"Name":"presentation:ExportsOutputFnGetAttamplifymonorepowebappforumapp01FF34A3AppId9A2F1BBF"}}

Stack admin
Resources
[~] AWS::Lambda::Function build-notifier/subscriber-function/base-function buildnotifiersubscriberfunctionbasefunction71C5A5E7 
 └─ [~] Environment
     └─ [~] .Variables:
         └─ [~] .APP_ENDPOINTS:
             └─ [~] .Fn::Join:
                 └─ @@ -17,6 +17,10 @@
                    [ ]     {
                    [ ]       "Fn::ImportValue": "presentation:ExportsOutputFnGetAttamplifymonorepowebappfeedsapp3A2C9EE9AppId1487D444"
                    [ ]     },
                    [-]     "\":\"FEEDS\"}"
                    [+]     "\":\"FEEDS\",\"",
                    [+]     {
                    [+]       "Fn::ImportValue": "presentation:ExportsOutputFnGetAttamplifymonorepowebappforumapp01FF34A3AppId9A2F1BBF"
                    [+]     },
                    [+]     "\":\"FORUM\"}"
                    [ ]   ]
                    [ ] ]
[~] AWS::Events::Rule build-notifier/build-sentinel buildnotifierbuildsentinel42E055FF 
 └─ [~] EventPattern
     └─ [~] .detail:
         └─ [~] .appId:
             └─ @@ -10,5 +10,8 @@
                [ ]   },
                [ ]   {
                [ ]     "Fn::ImportValue": "presentation:ExportsOutputFnGetAttamplifymonorepowebappfeedsapp3A2C9EE9AppId1487D444"
                [+]   },
                [+]   {
                [+]     "Fn::ImportValue": "presentation:ExportsOutputFnGetAttamplifymonorepowebappforumapp01FF34A3AppId9A2F1BBF"
                [ ]   }
                [ ] ]
[~] AWS::Lambda::Function scraper-notifier/subscriber-function/base-function scrapernotifiersubscriberfunctionbasefunction605AF0FD 
 ├─ [~] Code
 │   └─ [~] .S3Key:
 │       ├─ [-] 50976dca4512008b4dfb7e7aadc80e765589416ac7f7cea47624e6559103950d.zip
 │       └─ [+] d4f113888e632a6c489a029360492896b5df231df2527effccd349636cc63441.zip
 └─ [~] Metadata
     └─ [~] .aws:asset:path:
         ├─ [-] asset.50976dca4512008b4dfb7e7aadc80e765589416ac7f7cea47624e6559103950d
         └─ [+] asset.d4f113888e632a6c489a029360492896b5df231df2527effccd349636cc63441