milewski/cross-os

Allow adding OS-specific scripts in your package.json!

👨‍💻 Rafael Milewski

type Str = &'static str;

#[derive(Debug)]
enum Principle { SOLID, DRY, KISS, YAGNI, OPPA_GANGNAM_STYLE }

#[derive(Debug)]
struct Stack {
    languages: Vec<Str>,
    libs_and_frameworks: Vec<Str>,
    devops: Vec<Str>,
    databases: Vec<Str>,
}

#[derive(Debug)]
struct Profile {
    name: Str,
    from: Str,
    current_in: Str,
    principles: Vec<Principle>,
    tech: Stack,
}

fn main() -> () {

    let profile = Profile {
        name: "Rafael Milewski",
        from: "Brazil",
        current_in: "China",
        principles: vec![ Principle::SOLID, Principle::DRY, Principle::YAGNI, Principle::KISS ],
        tech: Stack {
            languages: vec![ "HTML/CSS", "Typescript", "PHP", "Dart", "Rust" ],
            databases: vec![ "Redis", "MySQL", "Meilisearch", "MongoDB", "SurrealDB" ],
            libs_and_frameworks: vec![
                "Vue.js", "React", "Svelte",
                "Webpack", "Vite", "Tailwind", "SASS",
                "Three.js", "Pixi.js",
                "Nuxt", "Next", "Nodejs",
                "Flutter", "NativeScript",
                "Laravel", "Nova", "GraphQL",
            ],
            devops: vec![
                "Linux", "Docker + Swarm", "Caddy", "Traefik", "Terraform",
                "CD/CI (Github Actions, Dagger, Drone)",
                "Monitoring (TICK Stack)",
                "Cloud Hosting (Alibaba Cloud, GCP, AWS, Vultr, DO)",
            ],
        },
    };

    println!("Hi, thanks for checking out my {:#?}", profile);

}

cross-os's Issues

An in-range update of @types/mocha is breaking the build 🚨

Version 2.2.43 of @types/mocha just got published.

Branch	Build failing 🚨
Dependency	@types/mocha
Current Version	2.2.42
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.9.4 to 10.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of @types/mocha is breaking the build 🚨

The devDependency @types/mocha was updated from 5.2.5 to 5.2.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Passing parameters to scripts

Hi,
Is there a way to pass parameters to the scripts within the cross-os: platform?
e.g.

"scripts": {
"foo": "cross-os bar"
}
"cross-os": {
"bar": {
"darwin": "echo $1", // will print 'Running on darwin'
}
}

npm run foo -- "Running on darwin"

Could this be installed as a devDependency instead?

npm i --save-dev cross-os? It's not needed in production, correct?

Yarn?

Am I wrong to wish this would work under Yarn?

TypeError: Cannot convert object to primitive value
      at /usr/share/yarn/lib/yarn-cli.js:77863:42
      at next (native)
      at step (/usr/share/yarn/lib/yarn-cli.js:91:30)
      at /usr/share/yarn/lib/yarn-cli.js:109:14
      at Promise.F (/usr/share/yarn/lib/yarn-cli.js:29304:28)
      at /usr/share/yarn/lib/yarn-cli.js:88:12
      at runCommand (/usr/share/yarn/lib/yarn-cli.js:77888:22)
      at Object.<anonymous> (/usr/share/yarn/lib/yarn-cli.js:77939:14)
      at next (native)
      at step (/usr/share/yarn/lib/yarn-cli.js:91:30)

Windows newlines in 1.2.0 packaged index.js

It seems like the 1.2.0 version of cross-os has windows newlines in index.js, causing execution to fail on non-Windows platforms.

Did you happen to do the publish from a Windows box without fixing the line endings first? :)

An in-range update of @types/node is breaking the build 🚨

Version 8.0.2 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	8.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Alternative to 'scripts' member in package.json

Thanks for a very useful package!

I use VSCode, and it it validating my package.json file against the schema in http://json.schemastore.org/project.

This flags the {} block added to scripts with a warning, as it is only expecting strings.

Would it be possible to have as an alternative a separate top-level member (eg. cross-os) that could also be used to define the cross-os scripts? This way, it would not trigger schema violations (for people that worry about that kind of thing!).

Something like:

  "scripts": {
    "clean": "cross-os clean-platform"
  },
  "cross-os": {
    "clean-platform": {
      "win32": "del /s /q dist",
      "darwin:linux": "rm -rf dist"
    }
  },

An in-range update of @types/node is breaking the build 🚨

Version 8.0.28 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	8.0.27
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Idea: automatically pick up the name of the package script

cross-os could automatically pick up the name of the package script (via process.env.npm_lifecycle_event):

{
  "scripts": {
    "user": "cross-os" // no argument!
  },
  "cross-os": {
    "user": {
      "darwin": "echo $USER",
      "win32": "echo %USERNAME%",
      "linux": "echo $USER"
    }
  },
  ···
}

Single command for “all non-Windows operating systems”?

Some commands work the same on all Unixes and only Windows is different. How do I specify such commands via cross-os?

I can see two options – both would be useful.

Option 1: "*" works the same as default in JavaScript’s switch statement:

"cross-os": {
  "chmodux": {
    "win32": "",
    "*": "chmod u+x main.js"
  }
}

Option2: Allow multiple comma-separated values:

"cross-os": {
  "chmodux": {
    "win32": "",
    "darwin,freebsd,linux,sunos": "chmod u+x main.js"
  }
}

For multiple Command

@milewski can you help me for this script example, i want to run "nodemon --exec python index.py" then "ionic serve", but nodemon part only execute and ionic part nothing happened

`{
"scripts": {
"ng": "ng",
"start": "ng serve",
"build": "ng build",
"watch": "ng build --watch --configuration development",
"test": "ng test",
"lint": "ng lint",
"eel":"cross-os eel1"

},
"cross-os":{
"eel1": {
"darwin":"nodemon --exec python3 index.py && ionic serve",
"win32": "nodemon --exec python index.py && ionic serve "
}
},
}`