hughsk/atom-node-resolver issues and pull requests

#31 - Fix incompatabilities with the newer Atom API

Pull Request - State: open - Opened by patgarner about 6 years ago

#30 - TypeError: Cannot read property 'command' of undefined

Issue - State: closed - Opened by wjuniorw over 6 years ago

#29 - Failed to activate the node-resolver package

Issue - State: open - Opened by lumaforge almost 7 years ago

#28 - Failed to activate the node-resolver package

Issue - State: open - Opened by aSapien about 7 years ago

#27 - Failed to activate the node-resolver package

Issue - State: open - Opened by amoshuang about 7 years ago

#26 - Failed to activate the node-resolver package

Issue - State: open - Opened by gilfuser over 7 years ago

#25 - Failed to activate the node-resolver package

Issue - State: open - Opened by WickedSik over 7 years ago

#24 - Failed to activate the node-resolver package

Issue - State: open - Opened by ghost over 7 years ago

#23 - Failed to activate the node-resolver package

Issue - State: open - Opened by jlsjonas almost 8 years ago

#22 - Failed to activate the node-resolver package

Issue - State: closed - Opened by Merujan99 almost 8 years ago

#21 - Failed to activate the node-resolver package

Issue - State: closed - Opened by maelsan almost 8 years ago

#20 - atom-node-resolver2

Issue - State: open - Opened by Kikobeats over 8 years ago

#19 - Failed to activate the node-resolver package

Issue - State: open - Opened by hamdshah almost 9 years ago - 2 comments

#18 - Failed to activate the node-resolver package

Issue - State: closed - Opened by zgababa about 9 years ago

#17 - Failed to activate the node-resolver package

Issue - State: open - Opened by MathijsvVelde about 9 years ago - 15 comments

#16 - Fix for 'Cannot read property 'command' of undefined', switch to new …

Pull Request - State: open - Opened by smarki about 9 years ago - 2 comments

#15 - Package.getActivationCommands is deprecated.

Issue - State: open - Opened by sasy-lingo over 9 years ago - 1 comment

#14 - Failed to activate the node-resolver package

Issue - State: open - Opened by vstepanyuk over 9 years ago - 20 comments

#13 - Command not found after installing and reboot atom

Issue - State: open - Opened by NelsonRock over 9 years ago - 5 comments

#12 - do not work

Issue - State: open - Opened by Jackong over 9 years ago - 4 comments

#11 - Package.getActivationCommands is deprecated.

Issue - State: open - Opened by ap0ught over 9 years ago

#10 - Use activationCommands instead of activationEvents in package.json

Pull Request - State: closed - Opened by davegomez over 9 years ago

#9 - Cannot read property 'command' of undefined

Issue - State: open - Opened by eschwartz over 9 years ago - 2 comments

#8 - Fix deprecation issues

Pull Request - State: open - Opened by forivall over 9 years ago - 2 comments

#7 - Deprecated Atom APIs will be removed June 1st

Issue - State: open - Opened by benogle over 9 years ago - 1 comment

#6 - Atom.Object.defineProperty.get is deprecated.

Issue - State: open - Opened by wmonk almost 10 years ago

#5 - Add support for ES6 `import`

Issue - State: open - Opened by stremlenye almost 10 years ago - 1 comment

#4 - Add support for NODE_PATH

Issue - State: open - Opened by lazdmx almost 10 years ago

#3 - #2 Add support for ES6 & JSX

Pull Request - State: open - Opened by charliedowler about 10 years ago - 1 comment

#2 - Unable to open files from scripts having JSX

Issue - State: open - Opened by techgyani about 10 years ago - 3 comments

#1 - Error trying to open dependencies that use harmony generators

Issue - State: open - Opened by juanmac over 10 years ago

Ecosyste.ms: Issues

GitHub / hughsk/atom-node-resolver issues and pull requests