Having issues with syntax highlighting - any suggestions?
fwiw my support has been highly lacking because I moved to creating my own IDE : http://alm.tools/ which gives me more freedom (and simplicity) to provide special TypeScript specific UI / UX / DX. You can use it today
npm install alm -g. But I do pop in here time to time cause I do care about Atom :rose:
Shameless plug : I used typedoc to create this : https://basarat.gitbooks.io/alm/content/features/documentation-view.html
Not as good as typedoc .... this is designed to be incremental for that quick insight on source code
I can't seem to
find much information on extending syntax highlighting or correcting issues with highlighting not functioning.
how do I disable this? because I use webpack to build project
TypeScript Badges: https://github.com/ellerbrock/typescript-badges
I'm following the Angular2 quick start project from angular.io and every time I make a change to a .ts file I'm seeing 13 pending requests appear in atom. Anyone have any idea why this is? I don't have this problem when I switch to an older quick start project based on Angular2 beta.
i tried what i could find online but nothing is working
"baseUrl": ".",
in tsconfig.json
but now i got the warning tsconfig is wrong
i also installed latest version of typescript
@bossqone
sorry typescript@latest
i guess lot people writing node modules with atom-typescript and got the same error when importing node modules
is there any fix?
If anybody is interested in the internals of this plugin, @mhartington was kind enough to do a video recording : https://www.youtube.com/watch?v=WOuNb2MGR4o I'm sorry I've moved on from this plugin myself personally but this video should help you understand how it works a bit more :rose:
can't find anything
Is there any recommanded way to compile and deply ones TS project? currently we compile everything into one hughe file via grunt script, but I would like to let atom compile the files seperately into some directory and then concatenate, minify and "uglify" them afterwards. The default atom settings seem to just compile every file and save it in the same directory as the TS file.
deply = deploy
I'm testing TS 1.9 in my project and of course Atom complains when using new options of TS 1.9 (for example the
lib option).
/**
- System configuration for Angular 2 samples
- Adjust as necessary for your application needs.
*/
(function(global) {
// map tells the System loader where to look for things
var map = {
'app': 'app', // 'dist',
'@angular': 'node_modules/@angular',
'angular2-in-memory-web-api': 'node_modules/angular2-in-memory-web-api',
'rxjs': 'node_modules/rxjs'
};
// packages tells the System loader how to load when no filename and/or no extension
var packages = {
'app': { main: 'main.js', defaultExtension: 'js' },
'rxjs': { defaultExtension: 'js' },
'angular2-in-memory-web-api': { main: 'index.js', defaultExtension: 'js' },
};
var ngPackageNames = [
'common',
'compiler',
'core',
'http',
'platform-browser',
'platform-browser-dynamic',
'router',
'router-deprecated',
'upgrade',
];
// Individual files (~300 requests):
function packIndex(pkgName) {
packages['@angular/'+pkgName] = { main: 'index.js', defaultExtension: 'js' };
}
// Bundled (~40 requests):
function packUmd(pkgName) {
packages['@angular/'+pkgName] = { main: '/bundles/' + pkgName + '.umd.js', defaultExtension: 'js' };
}
// Most environments should use UMD; some (Karma) need the individual index files
var setPackageConfig = System.packageWithIndex ? packIndex : packUmd;
// Add package entries for angular packages
ngPackageNames.forEach(setPackageConfig);
var config = {
map: map,
packages: packages
};
System.config(config);
})(this);
npm ERR! node v0.10.40
npm ERR! npm v2.13.3
npm ERR! file /home/agali/.atom/.apm/esprima/2.7.2/package/package.json
npm ERR! code EJSONPARSE
npm ERR! Failed to parse json
npm ERR! Unexpected token '\u0000' at 1:1016
npm ERR! data found!","homepage":"https://github.com/isaacs/inherits#readme"}
