atom-community / atom-ide-base Goto Github PK

View Code? Open in Web Editor NEW

45.0 45.0 14.0 2.25 MB

Atom IDE packages for Atom

Home Page: https://atom.io/packages/atom-ide-base

License: Other

JavaScript 96.23% TypeScript 2.05% Less 1.48% CSS 0.20% Python 0.02% Shell 0.02%

atom atom-ide hacktoberfest ide-packages

atom-ide-base's People

Contributors

Stargazers

Watchers

Forkers

uzitech bennypowers idleberg deankevorkian deedeeg lierdakil ayame113 cdaguerre bassforce86 keevan pulsar-edit

atom-ide-base's Issues

Installing “[email protected]” failed.

Installing the package from Atom results in this error:

Installing “[email protected]” failed.

npm ERR! code E500
npm ERR! 500 Internal Server Error - GET https://www.atom.io/api/packages/atom-ide-base/versions/3.4.

When I try to install the package from the repository I get this error:

54648 info lifecycle [email protected]~prepare: [email protected]
54649 verbose lifecycle [email protected]~prepare: unsafe-perm in lifecycle true
54650 verbose lifecycle [email protected]~prepare: PATH: C:\Users\user3948\AppData\Local\atom\app-1.60.0\resources\app\apm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\user3948\.atom\packages\atom-ide-base\node_modules\.bin;C:\Users\user3948\AppData\Local\atom\app-1.60.0\resources\app\apm\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\nodejs\;C:\Program Files\gdipp\;C:\Program Files\Git\cmd;C:\Users\user3948\AppData\Local\Programs\Python\Python39-32\Scripts\;C:\Users\user3948\AppData\Local\Programs\Python\Python39-32\;C:\Users\user3948\AppData\Local\Microsoft\WindowsApps;C:\Users\user3948\AppData\Roaming\npm;C:\Users\user3948\AppData\Local\atom\bin;;C:\Users\user3948\AppData\Local\GitHub\PortableGit_69bd5e6f85e4842f07db71c9618a621154c52254\cmd;C:\Users\user3948\AppData\Local\GitHub\PortableGit_69bd5e6f85e4842f07db71c9618a621154c52254\bin;C:\Program Files\Git\cmd;C:\Program Files\Git\bin
54651 verbose lifecycle [email protected]~prepare: CWD: C:\Users\user3948\.atom\packages\atom-ide-base
54652 silly lifecycle [email protected]~prepare: Args: [ '/d /s /c', 'npm run prepare.base && npm run prepare.nuclide' ]
54653 silly lifecycle [email protected]~prepare: Returned: code: 1  signal: null
54654 info lifecycle [email protected]~prepare: Failed to exec prepare script
54655 verbose stack Error: [email protected] prepare: `npm run prepare.base && npm run prepare.nuclide`
54655 verbose stack Exit status 1
54655 verbose stack     at EventEmitter.<anonymous> (C:\Users\user3948\AppData\Local\atom\app-1.60.0\resources\app\apm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
54655 verbose stack     at EventEmitter.emit (events.js:223:5)
54655 verbose stack     at ChildProcess.<anonymous> (C:\Users\user3948\AppData\Local\atom\app-1.60.0\resources\app\apm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
54655 verbose stack     at ChildProcess.emit (events.js:223:5)
54655 verbose stack     at maybeClose (internal/child_process.js:1021:16)
54655 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
54656 verbose pkgid [email protected]
54657 verbose cwd C:\Users\user3948\.atom\packages\atom-ide-base
54658 verbose Windows_NT 10.0.17134
54659 verbose argv "C:\\Users\\user3948\\AppData\\Local\\atom\\app-1.60.0\\resources\\app\\apm\\bin\\node.exe" "C:\\Users\\user3948\\AppData\\Local\\atom\\app-1.60.0\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\user3948\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\user3948\\.atom\\.apmrc" "install" "--target=9.4.4" "--disturl=https://atom.io/download/electron" "--arch=ia32"
54660 verbose node v12.14.1
54661 verbose npm  v6.14.13
54662 error code ELIFECYCLE
54663 error errno 1
54664 error [email protected] prepare: `npm run prepare.base && npm run prepare.nuclide`
54664 error Exit status 1
54665 error Failed at the [email protected] prepare script.
54665 error This is probably not a problem with npm. There is likely additional logging output above.
54666 verbose exit [ 1, true ]

windows 10
atom 1.60.0
node v12.14.1
npm v6.14.13

Provide more abstraction for overlays and float panes

They provide similar functionality, are similar in appearance, suffer from the same issues and even have similar codebases. I believe we could be more efficient at maintaining both datatip and signature help functionality if we combine it in a single package that provides two services.

Additionally, this one is now TypeScript'ified, while atom-ide-signature-help isn't.

Fixing modules resolving and dependencies

We should find a way to make modules/nuclide-* packages working. Should we use the original scripts?

    "dev-transpile": "./modules/nuclide-node-transpiler/bin/transpile.js",
    "release-transpile": "./modules/nuclide-node-transpiler/bin/release-transpile.js",

Is there a better easier way?

Failed to activate the atom-ide-base package

[Enter steps to reproduce:]

Atom: 1.58.0 x64
Electron: 9.4.4
OS: Unknown Windows version
Thrown From: atom-ide-base package 3.4.0

Stack Trace

Failed to activate the atom-ide-base package

At Invalid or unexpected token

C:\Users\57317\.atom\packages\atom-ide-base\package\main.js:1
(function (exports, require, module, __filename, __dirname, process, global, Buffer) { return function (exports, require, module, __filename, __dirname) { 
                                                                                                                                                           

SyntaxError: Invalid or unexpected token
    at new Script (vm.js:84:7)
    at NativeCompileCache.runInThisContext (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:148814)
    at Module.get_Module._compile (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:149668)
    at Object.value [as .js] (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:153485)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module._load (electron/js2c/asar.js:769:28)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:74:18)
    at customRequire (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:1:802772)
    at requireModule (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:14:1195622)
    at Package.requireMainModule (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:3520513)
    at Package.activateNow (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:3508497)
    at ~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:14:2607
    at Function.simpleDispatch (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:1186925)
    at Emitter.emit (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:1188366)
    at PackageManager.triggerDeferredActivationHooks (~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:386056)
    at ~/AppData/Local/atom/app-1.58.0/resources/app/static/<embedded>:11:384807

Commands

Non-Core Packages

activate-power-mode 2.7.0 
atom-ide-base 3.4.0 
atom-python-test 1.0.1 
atom-runner 2.7.1 
autocomplete-java 1.2.7 
basic-java-compile 0.4.0 
ide-python 1.9.7 
java-class-complete 0.0.6 
python-debugger 0.2.0 
python-docstring 0.0.3 
run-python-simply 0.6.0

Unimplemented pinned datatips and modifier providers

In the types for atom-ide-datatip, there are two unimplemented concepts:

a pinned datatip (presumably, a datatip that stays at a particular position in the editor until dismissed manually)
a modifier provider (presumably, a provider that is also passed the information about the held modifier keys like Ctrl or Shift)

What would be the use cases for these? So far I don't see much reason to have them. They aren't implemented by the LSP, so it's unlikely that we'll have proper language support for these either.

Eslint fails

> eslint .


Oops! Something went wrong! :(

ESLint: 7.19.0

TypeError: state.popChainContext is not a function
Occurred while linting C:\Users\aminy\atom-ide\nuclide\nuclide-commons\fsPromise.js:345
    at processCodePathToExit (C:\Users\aminy\atom-ide\node_modules\.pnpm\eslint@7.19.0\node_modules\eslint\lib\linter\code-path-analysis\code-path-analyzer.js:512:19)
    at CodePathAnalyzer.leaveNode (C:\Users\aminy\atom-ide\node_modules\.pnpm\eslint@7.19.0\node_modules\eslint\lib\linter\code-path-analysis\code-path-analyzer.js:729:9)
    at CodePathAnalyzer.overrideLeaveNode (C:\Users\aminy\atom-ide\node_modules\.pnpm\eslint-plugin-node@11.1.0_eslint@7.19.0\node_modules\eslint-plugin-node\lib\rules\process-exit-as-throw.js:130:27)
    at C:\Users\aminy\atom-ide\node_modules\.pnpm\eslint@7.19.0\node_modules\eslint\lib\linter\linter.js:954:32
    at Array.forEach (<anonymous>:null:null)
    at runRules (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\linter\linter.js:947:15)
    at Linter._verifyWithoutProcessors (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\linter\linter.js:1173:31)
    at Linter._verifyWithConfigArray (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\linter\linter.js:1271:21)
    at Linter.verify (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\linter\linter.js:1226:25)
    at LinterPrototype.verify (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint-plugin-only-warn\src\only-warn.js:14:55)
    at Linter.verifyAndFix (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\linter\linter.js:1416:29)
    at verifyText (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\cli-engine\cli-engine.js:239:48)
    at CLIEngine.executeOnFiles (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\cli-engine\cli-engine.js:807:28)
    at ESLint.lintFiles (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\eslint\eslint.js:521:23)
    at Object.execute (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\lib\cli.js:294:36)
    at main (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\bin\eslint.js:142:52)
    at Object.<anonymous> (C:\Users\aminy\atom-ide\node_modules\.pnpm\[email protected]\node_modules\eslint\bin\eslint.js:146:2)
    at Module._compile (node:internal/modules/cjs/loader:1108:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10)
    at Module.load (node:internal/modules/cjs/loader:973:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
    at node:internal/main/run_main_module:17:47

Tell us about your environment

ESLint Version: 7.19.0
Node Version: 15.8.0
npm Version: 6.14.11

What parser (default, @babel/eslint-parser, @typescript-eslint/parser, etc.) are you using?

I am using eslint-config-atomic

Please show your full configuration:

Configuration

{
  "extends": "eslint-config-atomic",
  "ignorePatterns": ["dist/", "node_modules/"]
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

atom-ide-base/nuclide/nuclide-commons/fsPromise.js

Line 345 in 8e952b4

const mode = typeof options !== 'string' ? options?.mode : null;

const mode = typeof options !== 'string' ? options?.mode : null;

eslint .

What did you expect to happen?
Lint

What actually happened? Please include the actual, raw output from ESLint.
An internal Eslint error happens

Are you willing to submit a pull request to fix this bug?
Not sure how to fix it

Mirror: #56

PHP IDE writes one

Installation fails on 1.54.0 on Windows when Atom is installed in a folder that contains spaces

This is due to a bug in package-deps.
Once it gets fixed on package-deps we must bump deps and ship a new atom-ide-base release.

Is it possible to format Python code?

Not sure if this is the right place to put this, but is it possible to format Python code using atom-ide-community?

Implement find references

I'm keeping atom-ide-ui only because of this https://github.com/facebookarchive/atom-ide-ui/blob/master/docs/find-references.md

Atom-ide-base enables/disables packages without warning

steelbrain/intentions#77

When there are packages that need to be enabled/disabled we should add a notification and lets the user choose to enable/disable them.

Nuclide Fuzzy Native test is failing

 FAIL  nuclide-fuzzy-native/__tests__/fuzzy-native-test.js
  ● fuzzy-native › can be required

    expect(received).toEqual(expected) // deep equality

    - Expected  - 1
    + Received  + 2

      Array [
        Object {
    -     "score": 1,
    +     "matchIndexes": Array [],
    +     "score": 0,
          "value": "test",
        },
      ]

      17 |     // The fallback uses a different scoring mechanism, so this will fail
      18 |     // if the native module failed to load.
    > 19 |     expect(matcher.match('test')).toEqual([{value: 'test', score: 1}]);
         |     ^
      20 |   });
      21 | });
      22 |

      at Object.<anonymous> (../nuclide/nuclide-fuzzy-native/__tests__/fuzzy-native-test.js:19:5)

Do we need the Datatip types in this repository?

Now that atom-ide-datatip has been converted to TypeScript, perhaps, we could move the types away from here and into the atom-ide-datatip repository.

The packages keep enabling and installing themselves

Okay, so someone decided it's a good idea to forcefully install enable all the atom-ide-* packages and forcefully disable any conflicts with no apparent way to turn this off. I'm pretty mad about this. At least let the user (me) choose what they want to use. I'm very close to flipping out and denouncing this organization completely at this point, because I hate this forceful approach with passion. I'm still on Atom because I've set up it exactly how I want it. I don't need any opinionated dev messing with my settings at all.

For now, I think I'm going to remove all atom-ide packages from my system and scrub the dependencies on those from my projects, because those get in the way of doing actual work. I hope that gives you some food for thought.

Best regards.

The packages keep installing and enabling by themselves.

Opening another issue, because the other one got snubbed and locked without any explanation, and the current situation is apalling.