Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build: update all non-major dependencies #21416

Merged
merged 1 commit into from
Jul 26, 2021
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 24, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
esbuild 0.12.15 -> 0.12.16 age adoption passing confidence
sass 1.35.2 -> 1.36.0 age adoption passing confidence

Release Notes

evanw/esbuild

v0.12.16

Compare Source

  • Remove warning about bad CSS @-rules (#​1426)

    The CSS bundler built in to esbuild is only designed with real CSS in mind. Running other languages that compile down to CSS through esbuild without compiling them down to CSS first can be a bad idea since esbuild applies browser-style error recovery to invalid syntax and uses browser-style import order that other languages might not be expecting. This is why esbuild previously generated warnings when it encountered unknown CSS @-rules.

    However, some people want to run other non-CSS languages through esbuild's CSS bundler anyway. So with this release, esbuild will no longer generate any warnings if you do this. But keep in mind that doing this is still potentially unsafe. Depending on the input language, using esbuild's CSS bundler to bundle non-CSS code can still potentially alter the semantics of your code.

  • Allow ES2021 in tsconfig.json (#​1470)

    TypeScript recently added support for ES2021 in tsconfig.json so esbuild now supports this too. This has the same effect as if you passed --target=es2021 to esbuild. Keep in mind that the value of target in tsconfig.json is only respected if you did not pass a --target= value to esbuild.

  • Avoid using the worker_threads optimization in certain old node versions (#​1462)

    The worker_threads optimization makes esbuild's synchronous API calls go much faster than they would otherwise. However, it turns out this optimization cannot be used in certain node versions older than v12.17.0, where node throws an error when trying to create the worker. This optimization is now disabled in these scenarios.

    Note that these old node versions are currently in maintenance. I recommend upgrading to a modern version of node if run-time performance is important to you.

  • Paths starting with node: are implicitly external when bundling for node (#​1466)

    This replicates a new node feature where you can prefix an import path with node: to load a native node module by that name (such as import fs from "node:fs/promises"). These paths also have special behavior:

    Core modules can also be identified using the node: prefix, in which case it bypasses the require cache. For instance, require('node:http') will always return the built in HTTP module, even if there is require.cache entry by that name.

    With this release, esbuild's built-in resolver will now automatically consider all import paths starting with node: as external. This new behavior is only active when the current platform is set to node such as with --platform=node. If you need to customize this behavior, you can write a plugin to intercept these paths and treat them differently.

  • Consider \ and / to be the same in file paths (#​1459)

    On Windows, there are many different file paths that can refer to the same underlying file. Windows uses a case-insensitive file system so for example foo.js and Foo.js are the same file. When bundling, esbuild needs to treat both of these paths as the same to avoid incorrectly bundling the file twice. This is case is already handled by identifying files by their lower-case file path.

    The case that wasn't being handled is the fact that Windows supports two different path separators, / and \, both of which mean the same thing. For example foo/bar.js and foo\bar.js are the same file. With this release, this case is also handled by esbuild. Files that are imported in multiple places with inconsistent path separators will now be considered the same file instead of bundling the file multiple times.

sass/dart-sass

v1.36.0

Compare Source

Dart API
  • Added compileToResult(), compileStringToResult(),
    compileToResultAsync(), and compileStringToResultAsync() methods. These
    are intended to replace the existing compile*() methods, which are now
    deprecated. Rather than returning a simple string, these return a
    CompileResult object, which will allow us to add additional information
    about the compilation without having to introduce further deprecations.

    • Instead of passing a sourceMaps callback to compile*(), pass
      sourceMaps: true to compile*ToResult() and access
      CompileResult.sourceMap.

    • The CompileResult object exposes a loadedUrls object which lists the
      canonical URLs accessed during a compilation. This information was
      previously unavailable except through the JS API.


Configuration

📅 Schedule: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate bot added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Jul 24, 2021
@google-cla google-cla bot added the cla: yes label Jul 24, 2021
@renovate renovate bot changed the title build: update dependency sass to v1.36.0 build: update all non-major dependencies Jul 26, 2021
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 12e0c78 to ec05208 Compare July 26, 2021 05:19
@clydin clydin merged commit 1e9be09 into master Jul 26, 2021
@renovate renovate bot deleted the renovate/all-minor-patch branch July 26, 2021 14:25
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Aug 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants