Anyone having issues with spacemacs throwing this error

Debugger entered--Lisp error: (file-error "Cannot open load file" "No such file or directory" "up-core")
  require(up-core)
  eval-buffer(#<buffer  *load*-21701> nil "/Users/me/.emacs.d/elpa/use-package-20171203.1313/use-package.el" nil t)  ; Reading at buffer position 1691
  load-with-code-conversion("/Users/me/.emacs.d/elpa/use-package-20171203.1313/use-package.el" "/Users/me/.emacs.d/elpa/use-package-20171203.1313/use-package.el" nil t)
  require(use-package)
  spacemacs-bootstrap/init-use-package()

I'm using Spacemacs and have a working .eslintrc on a sample React App. When I invoke checking on a .js file, I expect it to list the issues present, but instead, it suggests that javascript-eslint is disabled, although enable-able: Syntax checkers for buffer App.js in react-mode: javascript-eslint (disabled) - may enable: yes - executable: Found at /Users/will/src/learning/eslint-with-react/node_modules/.bin/eslint - config file: found . I'm obviously being stupid, what am I missing? I've read the flycheck documentation but can't get my head around this configuration.

so have you done a

fly-check enable

everytime I delete something using the d command, hitting p will undo my delete command instead of pasting what I copied from my OS

yeah, unfortunately

this is solved in vim by using registers besides the unnamed register

I believe evil has these built in, but I'm not exactly sure how to make sure your clip register and kill register aren't the same

a work around is to kill into registers that aren't the default one

so "adip which kills the paragraph into the a register

@alexkeyes in other words, it is pasting what's at the top of your kill ring -- which is the thing you just deleted.

that makes sense

is there any way to learn more about registers that isn’t just trial and error?

You could also cycle through your kill ring to get to the previous thing (after you p). I forget the default binding for that, but each time you hit it it'll switch the pasted text to the next earliest thing.

This looks decent: https://emacs-fu.blogspot.com/2009/01/using-registers.html

Tons more online about various solutions to your particular issue too.

eg https://www.reddit.com/r/emacs/comments/58lf3o/in_evil_mode_how_can_i_prevent_adding_to_the_kill/

Looks like C-p is the default binding for cycling through kill ring.

Personally I rely less on the kill ring than on an OS-level register-history app -- CopyClip on Mac, CopyQ on Linux.

But I def turn to the kill ring when I need it

@ag thank you for your help last night, it worked!

thanks for the info @eggsyntax!