Skip to content
#

build-tool

Here are 1,466 public repositories matching this topic...

A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

  • Updated May 2, 2022
  • JavaScript
gsoltis
gsoltis commented Apr 25, 2022

What version of Turborepo are you using?

1.2.5

What package manager are you using / does the bug impact?

npm, pnpm, Yarn v1, Yarn v2/v3 (node_modules linker only)

What operating system are you using?

Mac

Describe the Bug

turbo run build will hang if a package declares a dependency on itself in its package.json file.

Expected Behavior

turbo should display an error

good first issue
earthly
adamgordonbell
adamgordonbell commented Feb 23, 2022

Currently, when using explicit cache a single cache image can be specified to read from. It could be useful to have a priority-ordered list of images to check for cache hits. @mattste provided this use case:

Use Case

I'm attempting to do pull request previews where each pull request has its own Docker image. For pull requests that update a dependency (such as a package.json or mix.lock),

good first issue hacktoberfest type:proposal
orenmazor
orenmazor commented Apr 14, 2022

So this is not fully fleshed out in my head yet.

The gist is as such: my team currently uses makefiles + shell scripts to do things. this is obviously messy and awful.

I've done a few PoCs to migrate those things into taskfile and it's a beautiful world.

but here's the rub: we use shellcheck in all of our CI/vim/local machines/etc to verify shell scripts for various code smells.

I'd l

marvinhagemeister
marvinhagemeister commented Oct 20, 2020

Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.

I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in

enhancement help wanted good first issue reliability
jackkoenig
jackkoenig commented Mar 15, 2022

steps

I have reproduced the bug with both sbt 1.6.2 and 1.6.0, but no problem with sbt 1.5.8.

To reproduce, just take any SBT project using SBT 1.6 and try to compile with Scala 2.12.4, eg.

sbt new scala/scala-seed.g8
# cd into directory and change Scala version to 2.12.4
sbt compile

Note that the issue does not show up with Scala versions 2.12.2, 2.12.3, nor 2.12.5.

augustoproiete
augustoproiete commented Nov 21, 2020

Currently when calling the MSBuild alias with an MSBuildSettings, we need to set the target using the WithTarget extension method.

MSBuild("./my-app.sln", new MSBuildSettings
{
    Configuration = "Release",
    ToolVersion = MSBuildToolVersion.VS2019,
}.WithTarget("Build")); // <<<###

It would be nice if we could use a property, with a string, which would make it more na

style-dictionary
custa1200
custa1200 commented Oct 7, 2019

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b

tdyas
tdyas commented Apr 15, 2022

A user reported that include 'foo.thrift' from the same directory resulted in the file not being found. Thrift include statements include relative to the current directory first and then search include paths set by -I options. Pants dependency inference currently only infers a dependency for includes relative to a source root.

Pants should infer a dependency for same directory includes as

bschlenk
bschlenk commented Feb 24, 2022

Hey, really excited about this! The build times are really impressive.

With drafts: { nesting: true }, this css

.a {
  .b & {
    color: red;
  }
}

Results in the error SyntaxError: A nesting selector (&) is required as a prefix of each selector in a nested style rule.. I think it would be helpful to point out that this actually is valid syntax as long as the line i

enhancement good first issue

Improve this page

Add a description, image, and links to the build-tool topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the build-tool topic, visit your repo's landing page and select "manage topics."

Learn more