longlho / ts-transform-css-modules Goto Github PK

ts-transform-css-modules fails parsing the following example.ts file:

import "styles.css";

The reason for this seems to be that there is no importClause in this case.

The actual error is:

[at-loader]: Child process failed to process the request:  TypeError: Cannot match against 'undefined' or 'null'.
    at importVisitor (<snip>\node_modules\ts-transform-css-modules\dist\transform.js:38:35)
    at visitor (<snip>\node_modules\ts-transform-css-modules\dist\transform.js:76:28)
    at visitNodes (<snip>\node_modules\typescript\lib\typescript.js:49280:48)
    at visitLexicalEnvironment (<snip>\node_modules\typescript\lib\typescript.js:49313:22)
    at Object.visitEachChild (<snip>\node_modules\typescript\lib\typescript.js:49605:54)
    at visitor (<snip>\node_modules\ts-transform-css-modules\dist\transform.js:90:19)
    at Object.visitNode (<snip>\node_modules\typescript\lib\typescript.js:49229:23)
    at <snip>\node_modules\ts-transform-css-modules\dist\transform.js:97:27
    at <snip>\node_modules\typescript\lib\typescript.js:2492:86
<snip>

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

I'm trying to use this plugin using ttypescript (as you are mentioned as a reference plugin), I'm getting this error:

Module build failed: Error: tsconfig.json > plugins: "ts-transform-css-modules" is not a plugin module: {}

I can't find any specific docs on this...

Is it possible to use this transformer together with ts-loader, in order to transform CSS files automatically during the build?

Setup is webpack 3.3.0, ts-loader 2.3.1 and typescript 2.4.2.

According to the documentation of ts-loader, it should be possible to include custom transformers (getCustomTransformers()). I tried

const transformCss = require('ts-transform-css-modules');

module: {
    rules: {
        {test: /\.tsx?$/, use: [{loader: 'ts-loader', options: {getCustomTransformers: () => ({before: [transformCss()]})}}, 'tslint-loader']},

but I get an error message: TypeError: transformCss is not a function.

The devDependency @types/node was updated from 10.12.11 to 10.12.12.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 11.12.1 to 11.12.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Can you give an example of how this is used? Is it via tsconfig.json, webpack.config.js or something else?