yarnpkg

问题 I signed up for the Github private npm registry beta and followed their instruction: https://github.com/features/package-registry Works great with npm but I'd prefer using yarn. And while npm has no issues finding the registered package, yarn can't find it at all. yarn add @omniphx/adminite-adminite-ui-components outputs: yarn add v1.19.0 info No lockfile found. warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix

问题 I am encountering the following error when pushing to Heroku. Was working fine the other day. No major configuration changes on the commit I'm trying to push. I'm stumped at how to troubleshoot this. The Rails 5.1 application uses the following buildpacks: 1. heroku/nodejs 2. heroku/ruby I'm making use of webpacker and yarn. I think that has something to do with it but having trouble digging for more information. remote: -----> Preparing app for Rails asset pipeline remote: Running: rake

问题 I'm building a Rails 5.1.x rails app with jQuery and a few other libraries. Rails is insisting on having Yarn on, which is fine on development machine but I cannot have it on production. Is there a way to not have rails use Yarn by default? Remove yarn.lock and node_modules and everything else that comes with it. 回答1: When you create a rails project, you can add --skip-yarn as rails new app_path --skip-yarn . 回答2: Remove the following lines from the files bin/setup.rb and bin/update.rb - #

问题 I'm have a ReactJS application that uses the aws-sdk for cognito login. I used yarn to install all modules, but when I try to access the website at localhost I get a JS error: Uncaught (in promise) TypeError: STS is not a constructor . The error points to this line in the aws-sdk credentials file: this.sts = this.sts || new STS(clientConfig); Where STS is from: var STS = require('../../clients/sts'); Any thoughts on how to resolve this error? I've tried installing other modules or upgrading

问题 I was trying to run yarn global upgrade generator-jhipster but even though it seemed like it was working and installing the latest version, when I would run yo jhipster It would still be on an old version and would prompt me to run yarn global upgrade generator-jhipster I was running on OSX (Mac) I had just recently started using Yarn. I was previously using NPM but uninstalled NPM. $HOME/.config/yarn/global/node_modules/.bin was in my path, so that wasn't the issue. 回答1: When I switched over

问题 I ran yarn on my project on mac, generated a yarn.lock and committed it to git. Now I open the same project on a Windows machine, and run yarn to get the dependencies. It outputs yarn install v0.24.5 [1/4] Resolving packages... [2/4] Fetching packages... warning fsevents@1.2.4: The platform "win32" is incompatible with this module. info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... [4/4] Building fresh

问题 I just cloned this repository: react-native-paper but when I run on the root directory: $ yarn install I get the following warnings: D:\react-native-paper (master) (react-native-paper@2.4.0) λ yarn install yarn install v1.13.0 [1/4] Resolving packages... warning Resolution field "babel-core@7.0.0-bridge.0" is incompatible with requested version "babel-core@^6.26.0" warning Resolution field "babel-core@7.0.0-bridge.0" is incompatible with requested version "babel-core@^6.26.0" warning

问题 ignite-ir-boilerplate was not able to be installed. Is it a valid NPM module? Command failed: yarn add ignite-ir-boilerplate --dev Usage: yarn [options] yarn: error: no such option: --dev 回答1: You probably installed yarn using this: $ apt install cmdtest Use this instead: $ npm install --global yarn 来源： https://stackoverflow.com/questions/45430645/yarn-error-no-such-option-with-dev-flag

问题 I'm following this tutorials for install Bootstrap with Yarn this was the command for the new version of Bootstrap 4 on rails 5.1 who watch here: yarn add bootstrap@4.0.0-alpha.6 So I notice it was installed the bootstrap 4 alpha 6, JQuery3 and Tether. So it was already added on .gitignore the: /node_modules /yarn-error.log And was already Set up in my config/initializers/assets.rb Rails.application.config.assets.paths << Rails.root.join('node_modules') I need to put on my application.js //=

问题 My current workflow: name: Node CI on: [push] jobs: build: runs-on: ubuntu-latest strategy: matrix: node-version: [10.x] steps: - uses: actions/checkout@v1 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v1 with: node-version: ${{ matrix.node-version }} - name: npm install, build, and test run: | npm install yarn -g yarn yarn test env: CI: true NPM_TOKEN: ${{ secrets.NPM_TOKEN }} I have setup my NPM_TOKEN in the repo secrets area. The token is also in use on Netlify,