Getting "Cannot find module" when trying to use custom schematics with `new` command

[fxck]

There's little to no info about how to actually use schematics, so I tried forking @schematics/angular, changed couple things, published on npm (https://www.npmjs.com/package/@thescrollbar/schematics / https://github.com/thescrollbar/schematics), did following https://github.com/nrwl/nx/tree/master/packages/schematics#installing-nrwlschematics and tried

ng new impr --collection=@thescrollbar/schematics, which throws error listed below.. in case you are wondering, that path does exist on my filesystem and does link to this https://github.com/thescrollbar/schematics/tree/master/application

I also tried publishing contents of https://github.com/angular/devkit/tree/master/packages/schematics/angular to npm without changing anything and use it as schematics, didn't work either

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.4.2
node: 8.1.4
os: darwin x64

The log given by the failure.

Error: Cannot find module '/Users/fxck/.yarn-config/global/node_modules/@thescrollbar/schematics/application'
    at Function.Module._resolveFilename (module.js:485:15)
    at Function.resolve (internal/module.js:18:19)
    at new ExportStringRef (/Users/fxck/.yarn-config/global/node_modules/@angular-devkit/schematics/tools/export-ref.js:15:32)
    at NodeModulesEngineHost._resolveReferenceString (/Users/fxck/.yarn-config/global/node_modules/@angular-devkit/schematics/tools/node-module-engine-host.js:18:21)
    at NodeModulesEngineHost.createSchematicDescription (/Users/fxck/.yarn-config/global/node_modules/@angular-devkit/schematics/tools/file-system-engine-host-base.js:92:34)
    at SchematicEngine.createSchematic (/Users/fxck/.yarn-config/global/node_modules/@angular-devkit/schematics/src/engine/engine.js:63:40)
    at CollectionImpl.createSchematic (/Users/fxck/.yarn-config/global/node_modules/@angular-devkit/schematics/src/engine/collection.js:11:29)
    at Object.getSchematic (/Users/fxck/.yarn-config/global/node_modules/@angular/cli/utilities/schematics.js:40:23)
    at Class.run (/Users/fxck/.yarn-config/global/node_modules/@angular/cli/tasks/schematic-get-options.js:12:40)
    at Class.beforeRun (/Users/fxck/.yarn-config/global/node_modules/@angular/cli/commands/new.js:99:31)

[bmayen]

Barring documentation, it would be great if we could get some official feedback on whether or not we're even intended to be using this stuff yet. I get the sense that it's not production-ready for anything outside of the internal usage of it. But since there's no official word on this one way or another, a lot of us are very confused.

[fxck]

@hansl @Brocco maybe?

[fxck]

So after updating to 1.4.3 the error is gone!

..and is replaced by a different one Cannot find module '@thescrollbar/schematics/package.json'

[feloy]

I can make it work this way:
https://medium.com/@c1265a527848/95e22319cc24

[bmayen]

@feloy, thanks for putting this together! Looking forward to reading through this later tonight.

[bmayen]

@feloy, in the article you mention:

It is definitely not a perfect solution to place ourselves files in this node_modules directory, because files in the directory are generally handled by npm or yarn commands.

For users not able to publish their custom schematics and install via npm/yarn that way, npm link would be a better approach vs manually copying files into node_modules.

[fxck]

I just can't figure out how to make it as globally installable package, I can get it to work inside cli's node_modules, but as soon as I move it to global deps, it starts throwing tree.branch is not a function

[fxck]

I think I figured out at least one part. I thought that cli would be able to work with typescript schematics, but it actually has to be compiled first. So instead of just cloning https://github.com/angular/devkit/tree/master/packages/schematics/angular you actually need to clone and work with its npm run build command, you can then start changing packages/schematics/angular, I suppose there's a way to add your own schematics along it, but who knows on what places you need to chance stuff, so it's safer to just change the angular one... then you publish the dist folder to npm and THEN you can use it as a collection.. I have yet to try if I'll encounter the tree.branch problem.

[fxck]

Yep. Still getting tree.branch is not a function, works if I install my package globally with npm i -g @thescrollbar/schematics and then manually move it from /usr/local/bin/node_modules/ to /usr/local/bin/node_modules/@angular/cli/node_modules

[bmayen]

I'm also following this issue which is somewhat related. Would provide the ability to selectively extend the default collections.
angular/devkit#34

[fxck]

I hope there's going to be a way to set your collection as the default one so you don't have to use --collection=whatever anytime you try to generate something.

[fxck]

So when I try to do

ng g component --collection=@thescrollbar/schematics logo

it generates it using @angular/schematics instead, despite the fact that when I on purpose do

ng g shit --collection=@thescrollbar/schematics logo

it says

Schematic "shit" not found in collection "@thescrollbar/schematics".

which I think clearly indicates that it indeed is using my collection.. words can't even describe how frustrated I am

[fxck]

Closing this. All of my problems are actual known bugs.

Read more at https://stackoverflow.com/a/46431467/301596 (good piece of information about the state of schematics)